What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Why is there missing data in historic data reports?



When I generate a report with the historic data of some sensors, the sensor data is suddenly dropped or lost in the report. However, on the Live Data, 2 days, 30 days, and 365 days tabs in the PRTG web interface, PRTG correctly displays all data for these sensors.

Where is the missing data? How can I display this data in historic data graphs?

historic-data missing-values prtg reports

Created on Sep 8, 2014 2:51:10 PM by  Gerald Schoch [Paessler Support]

Last change on Jun 8, 2022 1:45:07 PM by  Brandy Greger [Paessler Support]

1 Reply

Accepted Answer



This article applies as of PRTG 22

Missing data in reports

Check your PRTG settings as listed below if you encounter the following issues in your historic data reports:

  • You see 0 values, or
  • you see data that is missing completely, or
  • you see data that is dropped for some sensors,
  • but PRTG correctly displays data on the sensor tabs.

1. Purging interval for historic sensor data

Check the purging interval for Historic Sensor Data under Setup | System Administration | Core & Probes | Historic Data Purging.

If the time span covered by your report exceeds the time span of the purging interval for historic sensor data, the data in your report is missing because the historic data of the sensors that is included in your report has already been deleted.

Increase the number of days that historic sensor data is kept. See also PRTG Manual: Core & Probes.

2. Scanning interval

The reason for missing data might also be a reduced scanning interval. Check if you have recently changed the scanning interval of these sensors.

To check it, go to the History tab of a sensor and take a look at the Message column. You know that the scanning interval has been changed if there is an entry that looks like this, for example:

Edited. Scanning Interval/Scanning Interval: 10 minutes

Why does a reduction of the scanning interval matter?

Internal test for incorrect calculations

When generating reports, PRTG ignores values in the calculation when an internally defined distance between two measurements is too big for a reasonable calculation.

The idea behind this mechanism is that if monitored values are too far apart, it is likely that there was a problem so that these values could cause an incorrect calculation. For example, overflows cannot be reliably detected in this case.

The formula for this time distance to ignore values for report calculations basically is

(3 * scanning interval) + (2 * timeout)

Note: This formula varies for different sensor types, based on our experience with particular sensors.


Consider an SNMP sensor that has a scanning interval of 300 seconds (5 minutes) and the SNMP timeout value is 5 seconds. So, the time span before which PRTG ignores values for the calculation is 3*300 (scanning interval) + 2*5 (timeout) = 910 seconds.

If you now reduce the scanning interval to 60 seconds (1 minute), PRTG only uses values from the last 190 seconds (3*60 + 2*5) for the report calculation. Because the scanning interval was 300 seconds before, PRTG now ignores all sensor values in the report calculation.

3. Spike filter in sensor channels

Check if you have set a spike filter in the channel settings of the sensor whose data is missing in your report.

The spike filter disregards very high or very low values that may result from faulty data transmission or incompatibilities on the monitored device. This setting prevents graphs from being unreadable.

Disable spike filtering if you want all measured values of the sensor to be written to your report.

Note: Use the spike filter with care. For SNMP sensors, check the SNMP compatibility options before you set a spike filter.


Sometimes, you might notice a difference between the result of a historic data report and the corresponding graphs for 2, 30, or 365 days in the PRTG web interface.

This can happen because the graphs that are available on the sensor tabs (graphs for 2, 30, or 365 days) are cached, while historic data reports always poll the data directly from the PRTG monitoring database stored on disk.

If the cached graph continues to look inconsistent, go to Setup | System Administration | Administrative Tools and try Recalculate PRTG Graph Data Cache (see PRTG Manual: Administrative Tools).

Created on Sep 8, 2014 2:57:03 PM by  Gerald Schoch [Paessler Support]

Last change on Dec 29, 2022 9:55:54 AM by  Brandy Greger [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.