Timezone inconsistency when generating PDF reports from Grafana dashboards

Description

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.

Environment

Grafana 6.7.3

Acceptance / Success Criteria

None

Attachments

1
  • 28 Sep 2020, 07:32 PM

Lucidchart Diagrams

Activity

Show:

Benjamin Reed November 18, 2020 at 5:57 PM

Merged to foundation-2020

Benjamin Reed November 16, 2020 at 5:25 PM

Alejandro Galue September 28, 2020 at 7:34 PM
Edited

One important thing to notice is what's mentioned in the attached screenshot.

The timezone setting in OpenNMS will be ignored by Grafana, if the dashboard has UTC, on the marked field. With Default it works, despite the issues reported above.

Fixed

Details

Assignee

Reporter

HB Backlog Status

Sprint

Affects versions

Priority

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

Flag notifications