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 comment