I had previously raised a consultation regarding the notifications mechanism and based on the reccomendations I have configured the notifications with the following parameters: (http://kb.paessler.com/en/topic/60552-do-closed-tickets-re-appear)
I have around 400 Wireless APs with only the ping sensor
The notifications are configured as:
If the Ping sensor falls into Fail state at least for 3 days raise a ticket,
if this condition continues for another 3 days, raise another ticket (which actually updates the previously raised ticket with a new date) and repeat this condition every 240 minutes (4 hours)
For some reason, after some days about half of my tickets stop being updated with a new date, but new duplicated tickets are created for the same devices.. I do not know why. So I receive a bigger list of the same devices with an old date and new tickets for the same devices with a new date.
Sometimes the tickets are closed automatically and the reason for this is "the condition ended", however, when I go to the sensor´s report, the sensor never went out of the down state. (For example I have a device that was removed about 1 month ago, and it is not there, so the ping is always in down state, but the ticket was closed automatically yesterday, because the "condition ended")
Can you help me with this issue, because I do not know what is the total number of devices in down state for at least for 3 days, so I do not know which of them should be given priority