When a Sensor Reports an Error

Dear tgrazka

The sensor status triggered by a limit cannot be delayed. However, you can delay the trigger of a notification. So while the sensor itself turns red immediately, the notification trigger can be configured to only create a ticket or send an email when the value is above a certain value for a certain amount of time.

And there is a gotcha unfortunately. Imagine an installation with 25 000 sensors and 5 000 of them are CPU Load sensors. In order to avoid large amount of emails with alerts for spiky high loaded CPU readings your manager asked you to delay email notifications for all these sensors with 5 minutes. As it was explained already in a thread https://kb.paessler.com/en/topic/64906-notification-change there is no way to multi edit notifications neither via web interface neither via API. How to achieve this without spending the whole week with dummy clicking?

Dear Tomasz

Up to 1000 sensors can get a notification using a library (each library is limited to 1000 sensors.) With five libraries covering 1000 sensors each, and a library notification for the primary channel for any included sensor, you can cover 5000 sensors.

I can see double inconsistency here: First one is with different definitions for sensor's error state when it is unreachable and when it overcomes limits - it should be the same one in my opinion. "When a Sensor Reports an Error" should apply for limits as well as for unreachable scenarios. Second one is when the only solution is to set notifications in two different places - on device and on library level. For me bulk edit for notifications would do the job.

Dear Tomasz

The option "When a Sensor Reports an Error" is intended to be used to prevent short-lived connection issues flooding PRTG with alarms. Beside this, PRTG intentionally shows the current state of the sensors. If a limit hits, it changes the sensor state.

Notifications triggered by the state "Down" include both sensor errors as well as errors caused by sensor limits, and can be configured to set a minimum time the state must be present before the notification triggers.

Notification bulk editing has some implications regarding consistency checks In many cases, notifications on libraries can provide the same or a similar effect and is easier to handle. For the time being we don't plan to introduce multi-edit for notifications, I am sorry.

Добрый день. Похожая ситуация. Отслеживаю работу программы через исходящую скорость сетевой карты. Поставил порог если скорость меньше 1 мбит/с выдовать ошибку. Данное условие хорошо работает на 95% PC. Но 5% часто выдают на один интервал значение равное 0 и PRTG это воспринимает за ошибку. Как недопустить ложные срабатывания.

Отслеживаю работу программы через исходящую скорость сетевой карты. Поставил порог если скорость меньше 1 мбит / с выставить ошибку. Это условие хорошо работает на 95% PC. Но 5% часто выдают на один интервал значение равное 0 и PRTG это воспринимает за ошибку. Как недопустить ложные срабатывания?

Dear dronorel,

in order to reach a wider audience, please communicate in English.