Reminder of the problem:
After a PRTG server restart, all acknowledged alerts appear as new alerts and are no longer acknowledged.
Once a sensor is acknowledged and either:
- the PRTG server is restarted, or
- the PRTG service is stopped and then restarted,
this sensor is no longer acknowledged. This happens at least once a month and forces the customer to search through support tickets each time to see if the alarm had already been acknowledged before the restart. A product update would be ideal.
Purpose of the product enhancement request:
preserve the acknowledgment status after a restart;
preserve the comment, author, and any acknowledgment due date;
do not resend a notification if the incident is identical to one already acknowledged;
restore the state after a restart without manual action;
If some customers wish to maintain the current functionality, you should be able to create an option to allow this in your update.
Reminder of the problem:
After a PRTG server restart, all acknowledged alerts appear as new alerts and are no longer acknowledged.
Once a sensor is acknowledged and either:
- the PRTG server is restarted, or
- the PRTG service is stopped and then restarted,
this sensor is no longer acknowledged. This happens at least once a month and forces the customer to search through support tickets each time to see if the alarm had already been acknowledged before the restart. A product update would be ideal.
Purpose of the product enhancement request:
preserve the acknowledgment status after a restart;
preserve the comment, author, and any acknowledgment due date;
do not resend a notification if the incident is identical to one already acknowledged;
restore the state after a restart without manual action;
If some customers wish to maintain the current functionality, you should be able to create an option to allow this in your update.