You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the time series request with "range" type and 10ms step, the returned data is rounded to seconds. This leads to bar-like graph and overlay of points.
Here the top graph is built with the "raw" query type and converted to time series with Grafana's tranformations. The bottom one is of "range" type. The queries are similar * | stats by(_time:10ms) count() and * | stats count().
And here everything is on one screen. Query, step, graph and response.
The query is correctly converted to VL query with step 10ms POST /select/logsql/stats_query_range?end=1733187154&query=%2A+%7C+stats+count%28%29&start=1733187134&step=10ms HTTP/1.1
The response from VL contains timestamps with millisecond precision.
Hi!
When building the time series request with "range" type and 10ms step, the returned data is rounded to seconds. This leads to bar-like graph and overlay of points.
Here the top graph is built with the "raw" query type and converted to time series with Grafana's tranformations. The bottom one is of "range" type. The queries are similar
* | stats by(_time:10ms) count()
and* | stats count()
.And here everything is on one screen. Query, step, graph and response.
The query is correctly converted to VL query with step 10ms
POST /select/logsql/stats_query_range?end=1733187154&query=%2A+%7C+stats+count%28%29&start=1733187134&step=10ms HTTP/1.1
The response from VL contains timestamps with millisecond precision.
But then the timestamps are rounded to seconds by datastore plugin or by Grafana.
The text was updated successfully, but these errors were encountered: