Also of note: removing the resample clause does allow the query to run successfully. Unfortunately the way the data comes in will require the extended resampling.
> On Dec 27, 2016, at 1:02 PM, Ryan January <[email protected]> wrote: > > I apologize, I neglected to include version information. I'm using 1.0.2 > installed via rpm, running on CentOS 7 > > On Tuesday, December 27, 2016 at 12:53:38 PM UTC-6, Ryan January wrote: > I'm running into an issue I haven't yet been able to understand yet. > > I'm trying to reduce the granularity of data in a measurement named > 'tablespace_utilization'. I would like the data at a daily interval by using > the following continuous query. > > CREATE CONTINUOUS QUERY tablespace_utilization_downsample ON telegraf > RESAMPLE EVERY 1d FOR 36h BEGIN SELECT max(bytes) AS bytes INTO > telegraf.autogen.tablespace_utilization_1d FROM > telegraf.autogen.tablespace_utilization GROUP BY time(1d), collection_host, > "database", tablespace_name, owner END > > Unfortunately I'm not seeing any evidence of this query running. In an > attempt to troubleshoot I reduced the group by and resample intervals down to > an hour. I was very surprised to find that the continuous query is running > exactly as I intended. > > CREATE CONTINUOUS QUERY tablespace_utilization_test_hr ON telegraf RESAMPLE > EVERY 1h FOR 2h BEGIN SELECT max(bytes) AS bytes INTO > telegraf.autogen.tu_test_hr FROM telegraf.autogen.tablespace_utilization > GROUP BY time(1h), collection_host, "database", tablespace_name, owner END > > > Data is being inserted into the 'tablespace_utilization' measurement every 5 > minutes. I have verified that data does exist within the time interval, and > no evidence of the query running is ever found in the influxdb log. Are there > any known issues with resampling periods of over 1 day? I'm stumped and > would appreciate any insight someone could provide. > > Thank you, > Ryan > > -- > Remember to include the version number! > --- > You received this message because you are subscribed to a topic in the Google > Groups "InfluxData" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/influxdb/FtBZauqAtrA/unsubscribe > <https://groups.google.com/d/topic/influxdb/FtBZauqAtrA/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/influxdb > <https://groups.google.com/group/influxdb>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/1958a6dd-631c-4505-92d6-070ec719b062%40googlegroups.com > > <https://groups.google.com/d/msgid/influxdb/1958a6dd-631c-4505-92d6-070ec719b062%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/0E2ABD3B-D361-4C33-A00C-855D330BE745%40gmail.com. For more options, visit https://groups.google.com/d/optout.
