Fixed
Details
Assignee
UnassignedUnassignedReporter
Daniel LukeDaniel LukeHB Grooming Date
Feb 28, 2023HB Backlog Status
Refined backlogComponents
Affects versions
Priority
Trivial
Details
Details
Assignee
Unassigned
UnassignedReporter
Daniel Luke
Daniel LukeHB Grooming Date
Feb 28, 2023
HB Backlog Status
Refined backlog
Components
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 27, 2023 at 9:02 PM
Updated February 28, 2023 at 8:51 PM
Resolved February 28, 2023 at 8:51 PM
With nodes (and humans) all over the world. we generally use UTC for monitoring (and syslogs etc.) so that it’s easier to correlate across systems.
OpenNMS running with TZ=Etc/UTC lets me choose time periods in UTC, but displays X values in the graph using my browser’s timezone (unlike other graphing platforms). This confuses my end-users.
eg. I’m in the Eastern timezone. If I graph traffic from Sun Feb 26 20:54:27 UTC 2023 → Mon Feb 27 20:54:27 UTC 2023 (aka ‘Last Day’) the first X value I see in the ‘Data’ tab is Sun Feb 26 15:55 and the final one is Mon Feb 27 15:50 (I see 15:55 and 15:50 if I hover over the first or last point in the graph).
The Raw values option in the Data tab does show a unix timestamp that gives the correct time (as expected).