What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Unique Alarm ID problem



Hi all,

We are trying to integrate PRTG to a third party application that we use to create support tickets for malfunctioned devices in our network.

In order to provide the infromation needed to our third party program, we try to get some sensor status data through ''EXECUTE HTTP ACTİON'' notification via ''POSTDATA'' variables, and generate an XML file; then pass this XML to our third party software.

So far, we are able to get some of the sensor status data of our interest via ''EXECUTE HTTP ACTION'' but we need to have a unique ID for each alarm, thus our tird party software knows that this specific alarm already been handeled (support ticket opened) or not.

In summary, we do not want to pass repetitive alarms to our 3rd party application.


http-action integration notifications ticket-system xml

Created on Apr 21, 2017 11:45:06 AM

1 Reply



Well, There is only 1 alarm per sensor. (its not per channel)

So use can you the %sensorID placeholder (https://kb.paessler.com/en/topic/373-what-placeholders-can-i-use-with-prtg)

Set the notification not to repeat, and it should only once when it goes down.

You may want to set PRTG to notify when the sensor goes back up, and log this in the ticket, or changes it priority/status

I have a similar setup for PagerDuty and its API.

Created on Apr 26, 2017 5:26:55 AM

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.