New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Support month and year as duration unit #3991

Open
ghost opened this Issue Sep 4, 2015 · 91 comments

Comments

@ghost
Copy link

ghost commented Sep 4, 2015

For example:

  • 1M for 1 month
  • 1y for 1 year

Its useful for me when i want to query the data last month and year...

@otoolep

This comment has been minimized.

Copy link
Contributor

otoolep commented Sep 4, 2015

@diiidiii -- how long is a month?

@beckettsean beckettsean changed the title Support month and year as duration unit [feature request] Support month and year as duration unit Sep 4, 2015

@beckettsean beckettsean added this to the Longer term milestone Sep 4, 2015

@beckettsean

This comment has been minimized.

Copy link
Contributor

beckettsean commented Sep 4, 2015

@diiidiii the challenge with supporting month or year durations is that they are not regular. It requires InfluxDB to be aware of things like variable month lengths, leap years, etc. This is a potential feature but certainly not a short-term one.

@ghost

This comment has been minimized.

Copy link

ghost commented Sep 7, 2015

they are not regular

Yes thats the reason why i need it. I know it isn't easy to implement but i just want to notify you that this will maybe a good feature. At the moment i use 30d, itsnt not always correct but its okay

@daviesalex

This comment has been minimized.

Copy link
Contributor

daviesalex commented Feb 29, 2016

Anybody that comes across this because Grafana is sending queries that have ''1y'' in them, see grafana/grafana#2874

The workaround to that bug is to set a minimum span on the grafana pane.

@dstreppa

This comment has been minimized.

Copy link

dstreppa commented Sep 1, 2016

+1

@jaapz

This comment has been minimized.

Copy link

jaapz commented Nov 25, 2016

Would be great to have this. It's not a trivial problem, but then again, InfluxDB is a time-series database, so it should have a good notion of what certain time durations are, right?

@gsemet

This comment has been minimized.

Copy link

gsemet commented Nov 30, 2016

Agree, I would like to be able to group by month or year and have grafana at least handle all subtilities automatically

@stantonk

This comment has been minimized.

Copy link

stantonk commented Dec 24, 2016

👍

@ryanmills

This comment has been minimized.

Copy link

ryanmills commented Jan 5, 2017

+1 need ability to group by time(1M) (month) or time(1y) (year)

@Wolfgang1966

This comment has been minimized.

Copy link

Wolfgang1966 commented Jan 8, 2017

I would also like to have the ability to group by month and year.

Thanks a lot

Wolfgang

@Wolfgang1966

This comment has been minimized.

Copy link

Wolfgang1966 commented Jan 8, 2017

@beckettsean By the way, days are not regular also ... thinking of DST switches, leap seconds a.s.o. :)

@tyhunt99

This comment has been minimized.

Copy link

tyhunt99 commented Feb 2, 2017

+1 need ability to group by time(1M) (month) or time(1y) (year)

as a time-series database isn't this sort of a standard feature?

@ale91x

This comment has been minimized.

Copy link

ale91x commented Feb 6, 2017

+1 need ability to group by time(1M(month)), (1y(year))

@xsherlockpl

This comment has been minimized.

Copy link

xsherlockpl commented Feb 6, 2017

I cant get solar production for the last month with just one query without that. +1

@olro

This comment has been minimized.

Copy link

olro commented Feb 23, 2017

+1 in general it is nice to have e.g. consumption data for water, electricity, gas on a per month/year basis

@m-tymchyk

This comment has been minimized.

Copy link

m-tymchyk commented Mar 7, 2017

+1 need ability to group by time(1M) (month) or time(1y) (year)

@smalenfant

This comment has been minimized.

Copy link

smalenfant commented Mar 8, 2017

+1 We derive bandwidth capacity by month, this makes it a little hard. Currently using 4w or 30d. Data not far off, just not exactly what the report viewer expects.

@mkren

This comment has been minimized.

Copy link

mkren commented Mar 8, 2017

+1

@gtt116

This comment has been minimized.

Copy link

gtt116 commented Mar 14, 2017

+1 need ability to group by time(1M) (month) or time(1y) (year)

@lcarsos

This comment has been minimized.

Copy link

lcarsos commented Mar 30, 2017

+1 grouping by 30d only gets you so far, and frustrates users when they compare against previous results and numbers for finished months change.

@cicciopizza

This comment has been minimized.

Copy link

cicciopizza commented Apr 5, 2017

+1 need ability to group by month / year. ex. 1M / 1Y

@mikegroot

This comment has been minimized.

Copy link

mikegroot commented Apr 5, 2017

+1

1 similar comment
@chfumero

This comment has been minimized.

Copy link

chfumero commented Apr 10, 2017

+1

@marine1988

This comment has been minimized.

Copy link

marine1988 commented Jun 19, 2018

+1

2 similar comments
@michielhub

This comment has been minimized.

Copy link

michielhub commented Jul 9, 2018

+1

@yihaozhadan

This comment has been minimized.

Copy link

yihaozhadan commented Jul 9, 2018

+1

@Pirx99

This comment has been minimized.

Copy link

Pirx99 commented Jul 13, 2018

After waiting too long for this important feature I now moved to a different DB. Sorry guys but without it you can't call it "time-series DB".

@gsemet

This comment has been minimized.

Copy link

gsemet commented Jul 13, 2018

We also moved to prometheus.

@cicciopizza

This comment has been minimized.

Copy link

cicciopizza commented Jul 13, 2018

we are also doing tests to migrate on prometheus...
shame because it was a good project...

@Pirx99

This comment has been minimized.

Copy link

Pirx99 commented Jul 13, 2018

I moved to PostgreSQL

@scmod

This comment has been minimized.

Copy link

scmod commented Aug 30, 2018

+1
from a large amount of data in timeunit of second, I have to draw the minutely, quarterly, half-hourly, hourly, daily, weekly, monthly or even yearly k-line chart, so I think group by month or year is really
powerful to do these things

@TheEggi

This comment has been minimized.

Copy link

TheEggi commented Sep 18, 2018

Any update on this one?

@scmod

This comment has been minimized.

Copy link

scmod commented Sep 27, 2018

Any update on this one?

currently not...

@aigr

This comment has been minimized.

Copy link

aigr commented Oct 1, 2018

+1

3 similar comments
@eraelpeha

This comment has been minimized.

Copy link

eraelpeha commented Oct 13, 2018

+1

@decaillet

This comment has been minimized.

Copy link

decaillet commented Oct 19, 2018

+1

@samreaves

This comment has been minimized.

Copy link

samreaves commented Oct 19, 2018

+1

@douglasg14b

This comment has been minimized.

Copy link

douglasg14b commented Oct 29, 2018

Would very much like to see this as a feature. It's not really possible to create any sort of month-by-month view in grafana for InfluxDB sources..... Unless the month is manually added as a tag.

@timhallinflux

This comment has been minimized.

Copy link
Contributor

timhallinflux commented Oct 30, 2018

Re-iterating @pauldix comment from above: This will be included as part of our new query engine, Flux. This would be something added to the window function in the new language.

Unfortunately, handling this in our existing query engine would be very difficult. Addressing many long standing query feature requests are exactly why we set out to create a new query engine and language with it.

This won't appear in the Flux 0.7 technical preview forthcoming -- but it is very much on our radar to include for GA of Flux.

@latonita

This comment has been minimized.

Copy link

latonita commented Oct 31, 2018

@timhallinflux

This won't appear in the Flux 0.7 technical preview forthcoming -- but it is very much on our radar to include for GA of Flux.

So what's the roadmap for flux and GA planned date? ;)

@blankroom

This comment has been minimized.

Copy link

blankroom commented Dec 2, 2018

+1 hope for the feature

@AleksBelytskyi

This comment has been minimized.

Copy link

AleksBelytskyi commented Dec 5, 2018

+1
I need this as well

@gkatzioura

This comment has been minimized.

Copy link

gkatzioura commented Dec 5, 2018

+1 It will be an awesome feature

@yysyp

This comment has been minimized.

Copy link

yysyp commented Dec 17, 2018

+1

1 similar comment
@thatguydan

This comment has been minimized.

Copy link

thatguydan commented Jan 1, 2019

+1

@murelli146

This comment has been minimized.

Copy link

murelli146 commented Jan 1, 2019

+1
GROUP BY time(1Y)
GROUP BY time(1M)

@dgnorton dgnorton added the 1.x label Jan 7, 2019

@frnandu

This comment has been minimized.

Copy link

frnandu commented Jan 10, 2019

+1

1 similar comment
@robinostlund

This comment has been minimized.

Copy link

robinostlund commented Jan 14, 2019

+1

@robcowart

This comment has been minimized.

Copy link

robcowart commented Jan 15, 2019

After discussions with a number of users in the energy sector, "quarterly" is also a valuable option. So...
GROUP BY time(1q)

@Hurleyking

This comment has been minimized.

Copy link

Hurleyking commented Jan 16, 2019

+1
GROUP BY time(1Y)
GROUP BY time(1M)
GROUP BY time(1q) "quarterly"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment