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!)
As a PRTG user, I want the PRTG cores/probes to be able to remember the last sensor state of objects prior to the core/probe server being rebooted and/or restarting the probe/core services, so that duplicate notifications are avoided.
Details of user story
For sensors where there are down/warning thresholds, these sensor thresholds execute a notification for the item. After the core/probe server and/or services restart, monitoring needs to restart as well for all sensors. In cases where the issue still resides on the sensor, once the sensor threshold is then met again, PRTG will send a duplicate notification on the issue. As a basic example, on a Saturday evening, a disk could fill to the point where the PRTG threshold is met and an email is sent to the responsible technician. As it is not a normal business day, the technician may choose to solve the issue on Monday. However, the core and/or probe servers reboot every Sunday automatically. Therefore, after rebooting on Sunday, there is a duplicate email notification thrown for the same disk full threshold. This is a basic example but the problem is exasperated by many sensors and notification methodologies across the PRTG infrastructure. The same phenomenon occurs if the respective probe or core server PRTG services are restarted.
- Criterion #1 - Create a global toggle option so that PRTG remembers down/warning sensors that already hit a notification threshold and executed their notification, and does not send a double notification after PRTG server/services restart and the asset is monitored again.