Datetime filter in Alert Rule follows the timezone from server while the graph in Alert Rule follows the timezone from browser

[douglas-wiliam]

I think that the problem here is that the plugin is converting the datetime from the two filter in image below to the timezone from server while the graph is defined in timezone from local browser generating to the user a bit of confusion in time define alert rules.

I verified it because my sever is configured in GMT-0 while my browser is in GMT-3 and the result in query is a graph forwarded 3h in future.

Grafana 10.0.3 running in Docker container
Ubuntu 22.04.3

[sdairs]

Thanks for the report @douglas-wiliam - @radchukd will be taking a look at this soon

[radchukd]

@douglas-wiliam what's your desired behaviour? You are right, in both cases, we take time that's given by grafana (server/browser).

[douglas-wiliam]

@douglas-wiliam what's your desired behaviour? You are right, in both cases, we take time that's given by grafana (server/browser).

@radchukd I think that is needed either a select list to define GMT or show the graph with the GMT from server as default instead the GMT from the browser how it is currently

c.c.: @gustavoaraujofe any other opinion?

[douglas-wiliam]

@radchukd some update about this?

I recently got a new problem in this context of graph and timezone:

1. This morning all my alerts stated as if they are in error:
   

2. It broken my Grafana -> Discord integration and made a bunch of alerts be fired when it weren't needed;

3. When I got in some of the alerts with error and run the preview for compare the result with the graph I noticed a divergence:

The graph don't shows up the correct value whilst the block "QUANTIDADE_ATUAL" accounts it correctly.

4. When I adjust the alert from "now-1d" to "now-2d" I realize that graph starts to show some value.

I think there is something more about this error I can't explain, but I think it is related to GMT used for the graph vs the GMT used by block "QUANTIDADE_ATUAL".