Fixed
Details
Assignee
Benjamin ReedBenjamin ReedReporter
Alejandro GalueAlejandro GalueHB Backlog Status
Backlog CMComponents
Sprint
NoneFix versions
Affects versions
Priority
Major
Details
Details
Assignee
Benjamin Reed
Benjamin ReedReporter
Alejandro Galue
Alejandro GalueHB Backlog Status
Backlog CM
Components
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created September 28, 2020 at 7:21 PM
Updated November 18, 2020 at 5:57 PM
Resolved November 18, 2020 at 5:57 PM
From the OpenNMS WebUI, when you want to generate a PDF report from a Grafana Dashboard, the user can choose the time range and a timezone.
Unfortunately, there is no correlation between these two. The time range is from the user perspective (i.e. the timezone from the user's browser).
When generating the report, the X-Axis that represents time on the graphs will respect the chosen timezone and transform the time range accordingly. That is not the case of the range mentioned at the beginning of the report, right before the selected timezone leading to confusion.
Two things need a fix here:
1) In the JasperReport templates, make sure to transform the time range mentioned in the report to be consistent with the chosen timezone and the actual X-Axis from all the graphs.
2) In the OpenNMS WebUI (the Angular app that handles the report generation), either adjust the time range when the timezone changes or add a note to be clear that the time range selection should be based on the user's timezone.