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

Sensor Delayed Down?

Votes:

2

Is it possible to add a delay to a sensors down state?

For example: Register a sensor as down only when the value of a sensor remains above the error threshold for 5 minutes. If the value goes below the threshold within these 5 minutes no alert should be generated.

I'm not looking to delay the notification, but the actual down state of the sensor.

delay down prtg

Created on Feb 11, 2013 4:27:38 PM



3 Replies

Accepted Answer

Votes:

0

Hello,

we are aware of this request, it's asked every now and then. But we really really don't want to make things more complicated in PRTG by introducing a latency on sensor state changes, where in the end you would have to consider two latencies until a trigger may be active or not, a dependency may be active or not (implementing this would most likely mean effectively killing the dependency feature and having all other sensors run into errors, while they could have been paused already). We decided and firmly believe that sensor state changes should happen immediately.

best regards.

Created on Feb 11, 2013 6:18:21 PM by Torsten Lindner [Paessler Support]

Last change on Feb 11, 2013 6:19:41 PM by Torsten Lindner [Paessler Support]



Votes:

0

Hi Wouter,

You can do this with a Custom Sensor that reads the result of the original sensor. If the value of the original sensor remains above a given threshold for a given number of minutes, you can set your Custom Sensor to a down state.

Regards,

Created on Feb 13, 2013 1:33:51 PM



Votes:

3

This feature would be incredibly valuable and I believe it is an error in judgement to not give users the option to have this feature.

What I suggest is a simple delay field which is a integer. For example, a delay of 3 would mean that the sensor had to be down for 3 consecutive cycles before it was marked as down. If a cycle was 5 minutes, the sensor would need to be down for 15 minutes (3x5) before it was triggered.

This would help reduce "noise" and errors that are short lived.

Created on Jun 6, 2013 5:45:57 AM




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.