All work
- The time range for the X-Axis of the graphs rendered by Backshift different than the resource page when using a different timezoneNMS-13102
- Add a warning when enabling forwarding metrics through the Kafka ProducerNMS-13039Resolved issue: NMS-13039Bonnie Robinson
- Missing documentation for how to use Kafka for Sink/RPCNMS-13038
- Multiple OpenNMS feature stop working when the Events Forwarder cannot push content to ElasticsearchNMS-13019Resolved issue: NMS-13019Dmitri Herdt
4 of 4
The time range for the X-Axis of the graphs rendered by Backshift different than the resource page when using a different timezone
Description
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Details
Assignee
UnassignedUnassignedReporter
Alejandro GalueAlejandro GalueHB Grooming Date
Feb 28, 2023HB Backlog Status
Refined BacklogComponents
Fix versions
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Alejandro Galue
Alejandro Galue
HB Grooming Date
Feb 28, 2023
HB Backlog Status
Refined Backlog
Components
Fix versions
Affects versions
Priority
Major
PagerDuty
PagerDuty
PagerDuty
Created January 22, 2021 at 6:37 PM
Updated February 28, 2023 at 8:56 PM
Activity
Show:
Jeff GehlbachFebruary 28, 2023 at 8:56 PM
Added as a watcher after resolving as a duplicate. Also promoting this issue to refined backlog.
In certain scenarios, users of the OpenNMS WebUI live in a timezone different than the OpenNMS server.
The WebUI shows times using the server timezone for everything. However, when rendering graphs via the Resource Graphs Page, even if the page shows a time range in the server's timezone, the graph rendered by Backshift uses the browser timezone, leading to inconsistencies and confusion, as shown in the attached screenshot (server has CST, whereas browser/client machine has EST as the timezone).
As almost everything else uses the server timezone, Backshift should respect that when rendering the graphs.