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
Timezone settings #18
Comments
Mh, timezones shouldn't be an issue, since the function which converts the unix (utc) timestamps to a human readable date runs on the client side / in your browser. The reason all history events display 08:00:00 as creation time is a bug though: When fnordmetric queries the history events from the "timeline set" it doesn't fetch their creation dates for performance reasons right now (they are stored in another set). So the 08:00:00 is really just a zero timestamp. I guess we should either remove the date from the list if we don't have it or actually fetch it from redis. What do you think? |
But there's something wrong though: I'm in UTC+1, it's 10:04 now. I have a timeline widget with a data point at 9:00 which increases now. the 10:00 datapoint is still at 0, so somehow - at least the timeline widget - isn't respecting my local timezone. I didn't look into the problem until now, but can anyone confirm what I'm seeing? (server and client timezone are the same) |
Hey I am getting the same problem my timeline graphs are out by 2 hours. Is the a way to over ride the time zone that the graphs are using. |
Finally I got some time to play with fnordmetric again. 😆 |
Fixes asmuth#18 hide time when time data is not retrieved from the redis
Do I need to configure the timezone?
At the event feed, the timestamps are shown in my timezone (GMT+8).
But in the history, all the events are at 08:00:00.
The text was updated successfully, but these errors were encountered: