a report for a sensor that was working fine before now shows no more data.
I recently changed the scanning interval from 5min to 1min.
No data in report
Modified on 2025-06-10 14:45:56 +0200
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.
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.
You changed the scanning interval from 5min to 1min on these sensors.
PRTG ignores values in the calculation that are too far apart. The formular for this distance is 3*interval + 2*timeout. The idea is that if the scanned values are further apart it is likely there was a problem and the values could cause a false calculation. Like overflows that can not be relieably detected in this case.
With reducing the scanning interval this distance changed from 910s to 190s. Since you were monitoring with a 300s interval all values are ignored.
You can get PRTG to use the values with setting a high SNMP timeout value (like 90s). If you have frequent timeouts in SNMP you should reduce the value again after the report to prevent a lot of sensor hanging in the timeout.
Jul, 2012 - Permalink