On Tue, Aug 23, 2016 at 1:57 PM, Andreas Gerstmayr <
[email protected]> wrote:

> Thanks for your response.
>
>
> > If server 2 doesn't send any data for a 10s time period then it won't be
> in the query returns. Server 2 should have a data point at 
> "2016-08-18T13:23:33Z"
> if it is reporting every 10 seconds. That would be included in the 
> "2016-08-18T13:23:30Z"
> SUM() bucket if it existed.
>
> Server 2 has a datapoint at "2016-08-18T13:23:33Z", but because of the
> WHERE time > 1471526615s AND time < 1471526650s it isn't included.
>

There's an ongoing effort to make "fill(previous)" be able to reach back
past the beginning of a query range so that the datapoint at 13:23:33 could
be included, despite the query lower bound being 12:23:35. That is not
ready, yet, however.

> Since all the buckets except the first and the last are correct, why not
> just expand your query range to include 10s extra at the beginning and the
> end, and then throw away those buckets?
>
> Is this possible within a single query? I'm using Grafana for visualizing with
> InfluxDB as the datasource, and imho there is no option to ignore the first
> and last row.
>

Without the fill(previous) behavior described above, I don't know of any
other solution. The database is properly returning the data being
requested, but the graphing windows don't line up with the query windows.

You could try using the GROUP BY time offset to make the interval
boundaries match up with the query time range boundaries, but that isn't
something Grafana supports in the UI, you'd have to manually edit the
queries.

https://docs.influxdata.com/influxdb/v0.13/query_language/data_exploration/#configured-group-by-time-boundaries


>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" 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/ms
> gid/influxdb/48efba06-a256-4445-a6ad-e3b2d37abc05%40googlegroups.com
> <https://groups.google.com/d/msgid/influxdb/48efba06-a256-4445-a6ad-e3b2d37abc05%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" 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/CALGqCvPsnuOUc-e8h8OQLMKkb%3DUSQyXkGfAdGStStZFA7cvjAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to