grafana goes crazy when timezone changes about grafana

[torkelo]

I will take a look at this soon!

[torkelo]

Now Grafana uses -5min, -1h, -1d etc whenever you use the relative time ranges. The selection zoom feature must use an absolute time range. And currently there is no way to send in absolute time ranges in UTC time (I have tried the &tz parameter but seems to be ignored when using the Graphite json render API).

I will have a look at opening an issue with the graphite-web project and maybe trying to fix it myself.

[xlson]

Couldn't you make it possible to configure grafana to be aware of what timezone the graphite installation is using and use that to "fix" the absolute queries before making them? Ofc adding tz support to graphite is nice but might take a bit longer.

[torkelo]

Can you try against latest master now? there is new setting in config.js called timezoneOffset. Set to 5 or "-0500". or what ever offset against UTC your browser/users are against the graphite server. This is not ideal but I think I need to fix the tz graphite parameter in order to improve on this (so I can send UTC times to graphite). The json API does not seem to care when I set the tz property.

[xlson]

Thanks.

This works but I had a lot of issues finding the right format to input the
offsets in. "-0100" did not work, "-1" and "0100" did, "1" is not the same
as 1. Maybe I'm just missing something but it was very confusing trying to
figure out the correct format.

/Leo

On Fri, Jan 24, 2014 at 5:05 PM, Torkel Ödegaard
[email protected]:

Can you try against latest master now? there is new setting in config.js
called timezoneOffset. Set to 5 or "-0500". or what ever offset against UTC
your browser/users are against the graphite server. This is not ideal but I
think I need to fix the tz graphite parameter in order to improve on this
(so I can send UTC times to graphite). The json API does not seem to care
when I set the tz property.

—
Reply to this email directly or view it on GitHubhttps://github.com/torkelo/grafana/issues/13#issuecomment-33235216
.