New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.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


Ping sensor delay after PRTG server restarst

Votes:

0

Your Vote:

Up

Down

Hi,

Alost every time after server restart, one of my specific ping sensor goes mad. Before restart it shows acceptable values like 0..10ms but sometimes, after I restarted the server hosting PRTG, this ping sensor shows values like 60...160ms.. I can quarantee that this is not true - I have alternative monitoring solution also set up, wich pings the same device and shows no anomalies. I'm suspicious, that after restart this specific ping sensor sends out queries at the same time as some other sensors are collecting data. I'm using some historical server to run PRTG.. Dell Poweredge 1850 with two Intel Xeon 3.2GHz and 8GB of RAM running on Windows 2008R2. How can I point out, that the problematic side is our server side not the device itself? System, Core and Probe healt are fine.. Only way to get rid of this problem is to play with specific sensor scanning interval. Any helpful ideas?

delay ping-sensor scanning-interval

Created on Jan 26, 2014 12:46:35 PM by  janx4 (0) 1



9 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

thank you very much for your KB-Post. May I ask, can you please upload a few screenshots showing the issue, and the "Settings"-Tab of this very Ping-Sensor?

best regards.

Created on Jan 27, 2014 2:12:10 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, Below You'll find 3 screenshots: 1. http://emu.standard.ee:81/PRTG/1.png - showing anomalies about 02.01 and 25.01 on this year. On 02.01 it just goes mad and at the moment I don't remember what I did exactly to fix this. Last time (25.01) I get this problem fixed by setting scanning interval to 5 minutes and after some time back. Also I restarted local probe. 2. http://emu.standard.ee:81/PRTG/2.png - image of settings tab. 3. http://emu.standard.ee:81/PRTG/3.png - image of sensor probe health

When I ping this device from command line on the same time on this server I see those anomalies too. When I ping this device from command line on the server next to it, I don't see those anomalies. This leads me to think that there is some congestion on this server at this very moment when it's pinging.

Created on Jan 28, 2014 7:55:58 AM by  janx4 (0) 1



Votes:

0

Your Vote:

Up

Down

Are there other sensors on the same device? If yes, this could indeed be sign of load to a certain extent, when PRTG starts, because it tries to get all sensors started as quickly as possible.
You could maybe try consider deploying a Remote Probe on this target, which would then continue monitoring if the PRTG Server is restarted
Does this also happen if you only restart the PRTG Services (and do not reboot the entire machine)?

Created on Jan 28, 2014 4:50:25 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

Yes. There are other sensors on the same device. Four SNMP traffic sensors (60 sec. interval) and one Sensor Factory Sensor (60 sec.interval) and one SNMP uptime sensor (1 h interval). Remote probe for just this device is not reasonable right now... I must check - restarting only services. But if I remember correctly, this also happends once if I upgraded PRTG components without restarting server itself..

Created on Jan 28, 2014 5:17:08 PM by  janx4 (0) 1



Votes:

0

Your Vote:

Up

Down

Maybe it changes something if you set the Ping sensor to a smaller interval (30 seconds), and/or setting the Ping Sensor to send multiple ping packets per scan.

Created on Jan 29, 2014 9:46:05 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Must try. I hav not changed it to a smaller.. Basically, if I have restarted the server and when I'm going to see anomalies, I'm going to play with those settings already to get things fixed. May I ask, how are sensors workload distributed? is there any logic behind that to avoid scanning constantly on the same time..? To avoid peaks like that I'm suspecting right now? Any way to change sensor startup time on the same device like T+ 38 sec. os smthng like that?

Created on Jan 31, 2014 11:46:38 AM by  janx4 (0) 1



Votes:

0

Your Vote:

Up

Down

After a restart of PRTG, all sensors of one device scan in quick succession to get all sensors running quickly. Once they show results, the scans are evenly distributed according to the scanning interval(s) of the sensors, so that possibly no peaks appear.

Created on Jan 31, 2014 11:56:17 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Does this distribution works also between devices? I'm mean, what is the chance of overlapping, if I use like 10 device with ping sensor and they all are configured using 60 sec. inteval. How big is the possibility that let's say 4 devices will be pinged at the same time(frame) ?

Created on Jan 31, 2014 12:01:02 PM by  janx4 (0) 1



Votes:

0

Your Vote:

Up

Down

The distribution is mostly done on a per-device basis. Distributing all sensors of all devices evenly is of course also attempted, but much harder due to the different scanning intervals. It's not possible to judge the chance of x devices being pinged at the same time, there is a huge random factor involved, as this will change with each run / start of the PRTG services.

Created on Jan 31, 2014 12:05:42 PM by  Torsten Lindner [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.