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

PRTG Network Monitor

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

Free Download

Top Tags


View all Tags

Scaning Interval don't be respect in Live Data.

Votes:

0

Your Vote:

Up

Down

We are running a very long PRTG instalation, everything was OK without any change, but recently we have in some sensors (not all) (SNMP custom) a non-sync Scaning interval.

The setup is for Scaning interval 30s, and we can see Live Data table entries for 30s but also 60s. Please see attach. The sensor allways report 100% coverage.

We don't understand why we dont have allways 30s entries, and have a mix of 30s and 60s. Nothing was change. 1 Core with 2 Probes, everything already reboot, also debug, pause all sensors and just Play with few and same situation.

Any idea where we can look to fix this? https://freeimage.host/i/5VpoPa

prtg sensor snmp

Created on Nov 11, 2021 10:40:05 AM by  Daniel Ribeiro da Silva (0) 1



2 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

Please note that we don't support/recommend scanning interval faster than 60s for Sensors which are not Ping Sensors. According to your screenshot, I suspect an issue with the scheduler which is not able to run all scan queries in the given time. This occurs specially if many Sensors run in a faster scanning interval.

Created on Nov 15, 2021 2:48:29 PM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks for your reply We already do more debug and we find some devices was with wrong "Overflow" option.

SNMP Compatibility Options/Overflow Values: Handle overflow values as valid results (the correct one for our case)

The only caracteristic possible to validate was the wrong values in Scanning Interval, without any error reported. After we change this SNMP value everything back to normal, and Scaning Interval complete every 30s.

Created on Nov 15, 2021 4:14:40 PM by  Daniel Ribeiro da Silva (0) 1



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.