New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

150.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Why is there missing data in historical data reports?

Votes:

0

Your Vote:

Up

Down

When I generate a report with the historical data of some sensors, the sensor data suddenly is dropped or lost in the report. However, on the tabs in the PRTG webGUI for live data, 2 days, 30 days, and 365 days, PRTG displays all data correctly also 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]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 13 or later

Missing Data in Reports

If you encounter historic data reports that show no data or dropped data for some sensors but PRTG displays all data correctly on the sensor tabs, please check if you have changed the scanning interval of these sensors recently. The reason for missing data might be a reduced scanning interval.

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.

Example

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.

Showing the Missing Values in Reports

If you want PRTG to use these values in your reports, try increase the SNMP timeout value in section Credentials for SNMP Devices of the parent device of the sensor (or on group, probe, or root level), for example, to 90 seconds.

Attention: This workaround might result in frequent timeouts of SNMP sensors. In this case, please reduce the timeout value again after you generated a report to prevent sensors from hanging in the timeout.

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

Last change on Sep 9, 2014 1:04:28 PM by  Gerald Schoch [Paessler Support]



Please log in or register to enter your reply.


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.