Network Management

Last Month data in custom table report display incorrect dates for SolarWinds Platform 2024.2.1 and below

A custom report with data source set to 'from Last Month' and produces historical statistic data in a table format contains data from two months ago. When the report is generated, it produces not only the data points for the whole month but also from the last day of the previous month. For example, the caption says 'Statistics from Last Month (Mar 1 - Mar 31, 2016)', but the report still contains data from the last day of the previous month (Feb 29, 2016) in the output.

First published date

11/8/2018 7:32 PM

Last published date

2/25/2025 4:51 AM

Overview

A custom report with data source set to 'from Last Month' and produces historical statistic data in a table format contains data from two months ago.

When the report is generated, it produces not only the data points for the entire month but also from the last day of the previous month. For example, the caption says 'Statistics from Last Month (Mar 1 - Mar 31, 2016)', but the report still contains data from the last day of the previous month (Feb 29, 2016) in the output.

Product section

Orion Platform

Cause

The issue occurs because date/time data can be stored in both UTC and local time in the SolarWinds environment.  When the date/time data stored in the database is different, generated reports may be incorrect when factoring in daylight saving time (DST) changes.  

In some scenarios, if the data is in the same time zone as the SQL Server, the generated report does not have a problem.

Resolution

Starting in SolarWinds Platform 2024.4 and above, there are two setting (by default are off) to address this issue:

  • AdvancedDateTimeCalculationOption
  • SQLServerTimezone

AdvancedDateTimeCalculationOption will try to evaluate and calculate difference in the data for local time compared to UTC when generating reports.  For more information, refer to the following documentation.

Note: Moving the machine (where SolarWinds Platform is installed) to the same time zone where the SQL Server is installed is strongly recommended.  If it is not possible, you can set the "SQLServerTimezone" in the Advanced Setting to the proper time zone.  Refer to the following documentation.