We are using a external ticket system. For creatings tickets in the external system we send alarm notification to our ticket system. This system creates new ticket for this "down" devices.

It whould be very nice to have a unique alarm id. so if a up-notifiaction is send to the ticket system, the ticket system can search for this alarm id an will close the ticket automaticly.

Article Comments

Hello,

thank you very much for this support ticket. I'm afraid such a unique ID is not available (maybe the time stamp & sensor ID can be used in your ticket system for identification).

best regards.


Aug, 2014 - Permalink

You can use your own notification script/executable and within that script/executable you can create/maintain your own unique notification IDs, based on device ID, sensor ID, status, date/time, etc.

Execute Program

https://www.paessler.com/manuals/prtg/notifications_settings

https://www.paessler.com/manuals/prtg/custom_notifications

https://helpdesk.paessler.com/en/support/solutions/articles/76000041685-how-can-i-use-the-prtg-application-programming-interface-api

Placeholders/Variables: https://https://helpdesk.paessler.com/en/support/solutions/articles/76000063844

I usually solve these kind of challenges by sending a syslog alert to a remote system and then 'attaching/listening' to the syslog file with a perl script that maintains state within a sqlite database.

Regards Kurt


Aug, 2014 - Permalink