Since updating to 18.1.38.xxx+, our alarms will no longer self acknowledge after shooting off an e-mail to our ticketing system. Is there a setting I am missing, or was the behavior of this changed? Previously, Sensor A alarms, after 5 minutes if it does not clear an e-mail is sent to our ticking system. As soon as the e-mail is sent, Sensor A automatically enters acknowledged state. As of now, it remains as an active alarm even after the e-mail is sent and I have to manually acknowledge the alarm indefinitely.
Article Comments
Ah ha. This led me in the right direction (thanks!), but I'm not sure how to fix it.
Under the notification action, we have it set to send to our ticketing system. Once that is done, its set to execute HTTP action as follows (some info changed (caps) for privacy):
https://IP OF SERVER/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Requested&username=USERNAME&passhash=PASSHASH
If this is what needs to change, I'm honestly not quite sure how to change it or what to change it to.
Mar, 2018 - Permalink
Unfortunately, no. Sensors that go down remain unacknowledged even after a ticket has been generated. Is it possible that the password hash has changed due to the security vulnerability? It's tied to my account apparently and I did have to change my password after updating PRTG.
Right now we are on 18.1.38.11934+
Mar, 2018 - Permalink
Most likely yes, the passhash has been changed from your password getting updated.
Mar, 2018 - Permalink
Thank you. I was able to get the new hash here: https://PRTG DOMAINorIP/api/getpasshash.htm?username=ENTERUSERNAME&password=ENTERPASSWORD
I will see if that works or not with the API.
Mar, 2018 - Permalink
It sounds like you have a notification that kicks off an API call to set the sensor to acknowledged.
If so, then those settings for that sensor may need to be adjusted.
Can you confirm this by checking the Notification Settings for the sensor in question?
Mar, 2018 - Permalink