Skip to content
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.

Timestamp in query will not use UTC #330

Closed
denen99 opened this issue Apr 30, 2021 · 1 comment
Closed

Timestamp in query will not use UTC #330

denen99 opened this issue Apr 30, 2021 · 1 comment

Comments

@denen99
Copy link

denen99 commented Apr 30, 2021

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

  1. 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)
  2. remove the time macro
  3. Group by time(1min,none)
  4. Launch Query inspector
  5. See incorrect dates being used

Specifications

  • Version: 2.0.2
  • Platform: Linux
  • Grafana Version: 7.4.3
@denen99
Copy link
Author

denen99 commented Apr 30, 2021

sorry my mistake, we were on 2.0.1, not 2.0.2 where it looks like these are fixed. We thought 2.0.2 was publicly listed as an official release

@denen99 denen99 closed this as completed Apr 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant