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
{{ message }}
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.
using version 2.0.2, we are still seeing the issue of incorrect timezones being used. We have tried changing the local browser timezone to no effect, the query inspector still shows the timestamp query using a local timezone instead of UTC. Choosing the option "Convert timefilters to UTC" has no effect on the query being executed.
We are using a partitioned table using a column timestamp (not ingestion based, so no pseudo params of _PARTITIONTIME are needed)
Expected Behavior
The timestamp used in the query will use UTC based dates/times
Actual Behavior
Local browser based dates/times are used and will not use UTC
Steps to Reproduce the Problem
Create a new query, for the timestamp column, choose a DATETIME based column that you are all also partitioning on (in our case it was just called timestamp)
remove the time macro
Group by time(1min,none)
Launch Query inspector
See incorrect dates being used
Specifications
Version: 2.0.2
Platform: Linux
Grafana Version: 7.4.3
The text was updated successfully, but these errors were encountered:
Bug Report
using version 2.0.2, we are still seeing the issue of incorrect timezones being used. We have tried changing the local browser timezone to no effect, the query inspector still shows the
timestamp
query using a local timezone instead of UTC. Choosing the option "Convert timefilters to UTC" has no effect on the query being executed.We are using a partitioned table using a column timestamp (not ingestion based, so no pseudo params of _PARTITIONTIME are needed)
Expected Behavior
The timestamp used in the query will use UTC based dates/times
Actual Behavior
Local browser based dates/times are used and will not use UTC
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: