Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] Local browser time should not be used for absolute dates when timezone is UTC #12817

Closed
balakrishnabk opened this issue Aug 6, 2018 · 2 comments

Comments

@balakrishnabk
Copy link

Read before posting:

Please include this information:

What Grafana version are you using?

Grafana v5.2.1 (commit: 2040f61) version

What datasource are you using?

influxdb

What OS are you running grafana on?

ubuntu

What did you do?

select absolute dates for querying

What was the expected result?

the timeline should be same and use UTC instead of local browser

What happened instead?

the calculations are based on browser time when absolute dates are selected

If related to metric query / data viz:

Include raw network request & response: get by opening Chrome Dev Tools (F12, Ctrl+Shift+I on windows, Cmd+Opt+I on Mac), go the network tab.

Reference with screenshots.
https://community.grafana.com/t/grafana-influxdb-difference-resultset-in-previous-week-vs-timerange-filter/9054

@marefr marefr changed the title [InfluxDB] Difference resultset in Previous week vs timerange filter (local browser time for absolute dates) [Bug] Local browser time are used for absolute dates Aug 6, 2018
@marefr marefr added this to the 5.3 milestone Aug 6, 2018
@marefr marefr changed the title [Bug] Local browser time are used for absolute dates [Feat] Local browser time are used for absolute dates when timezone is UTC Aug 6, 2018
@marefr marefr changed the title [Feat] Local browser time are used for absolute dates when timezone is UTC [Feat] Local browser time should not be used for absolute dates when timezone is UTC Aug 6, 2018
@marefr marefr removed this from the 5.3 milestone Aug 6, 2018
@marefr
Copy link
Member

marefr commented Aug 6, 2018

Changing this to feature instead of bug. Seems this has worked this way since at least Grafana v4.1.0 and I haven't found any other issue related to this.

@pkolyvas
Copy link
Contributor

We're in the process of moving Grafana feature requests to GitHub Discussions. I'm closing feature requests that have seen limited from the community and/or the Grafana team.

Should this feature still be of interest to you, please re-create it in our Discussions area. In doing so the community can continue to contribute to exploring, confirming and sharing their use cases (and more).

As with all things Grafana, we value your input and participation in this project and appreciate your patience during this transitional period. Should you wish to connect to discuss anything Grafana-related, I have an open door policy and my contact details are on my GitHub profile page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants