New Question
 
 
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 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


Delay PRTG sensor alarm error state

Votes:

10

Your Vote:

Up

Down


Want this feature implemented, too? Please upvote by clicking Thumbs up!

(Posts as a reply won't be published in this feature request thread. Read Me!)


User Story

As a PRTG User, I want to have a possibility to delay the sensor alarm error state by a definable number of consecutive errors to minimize false positive messages/alarms.

Details of User Story

We would like that you implement a function to put a sensor into error status only if after a definable number of consecutive errors, the error still exists. Therefore, you would have to implement a kind of error counter, which resets when the status of the sensor is OK again.

We often have the situation that we monitor some applications which temporary throw some errors only for one polling interval, but the application do not really have a problem. In the next one or two polling intervals everything will be fine. However for these intervals the sensor goes to the error state and we get it mentioned at our dashboards.

This also applies e.g. for CPU sensors. Sometimes there are some spikes in one polling interval, which are totally normal for a CPU of an server and don't have to lead into an alarm. With the mentioned feature, it would be possible to filter this kind of CPU spikes.

In both situations we can't do anything but we see this "false-positive" errors, what leads to confusion under our colleagues.

Acceptance criteria

  • The feature to delay sensor alarm error state is implemented
  • We can freely define at each sensor the number of consecutive errors, which puts the sensor into error state (error count)
  • It is not necessary to define this value for each sensor. It have to be an optional feature for each sensor. If this value is not defined for the sensor, the standard behaviour must work and the sensor must go directly after one error into error state.
  • The feature must not affect the setting options for limit values or lookups.

Status

Open

add-feature error-delay prtg-kbtracker

Created on Jun 17, 2020 2:04:56 PM by  nkamprad (10) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

This is partially already possible. In the "Settings" of a sensor under "Scanning Interval" you can select for how many scans the sensor should remain in "Warning" state before going "Down".

Please note, that this only applies to failed queries, if a set limit is reached the sensor will go Down immediately (same goes for a status set by a lookup).

Created on Jun 18, 2020 9:23:55 AM by  Sasa Ignjatovic [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Sasa,

Sure, that we already know. However, that do not help us in the mentioned and the most other situations, because it only applies to failed queries. We need this feature primary for reached limits or error states caused by lookup values.

Best Regards, Norman

Created on Jun 18, 2020 9:38:03 AM by  nkamprad (10) 1



Votes:

0

Your Vote:

Up

Down

Hi, may be you can do the workaround to delay the notification. There is a option to trigger notification after the sensor is down for X seconds. Besrt regards, Karsten

Created on Jul 13, 2020 1:35:56 PM by  luchs (0)



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.