Hello,

We will open a ticket in another external tciket tool (CA SDM).

How should this be done in the PRTG?

Will we have to execute trigger calling a call system API, passing the PRTG variables? Is there any documentation to support us?

When we close the ticket in the external ticket tool, we want the alarm to be closed too. That is, in the ticket tool I will need to pass an API call to close the alarm. It is possible?

Thank you.

Article Comments

Hello Sandro, we appreciate your contact.

Creating a ticket in a 3rd party system (with HTTP API) when an notification is triggered is relatively simple. Please have a look here:

However, it's not possible to "close" an Alert. If the sensor's status changes to Warning or Down, it will only leave that state when the thresholds are modified or when the issue ceases. Otherwise, the sensor can either be paused for a specific period of time or in definitively or it can be "Acknowledged", which shows a slightly different red color and stops sending new alerts for the sensor.

But effectively, you cannot "close/stop" an alert in PRTG without locating the source of the issue and fixing it or modifying the thresholds for alerting to disable the alert. Here's a similar question/case:

Best Regards,
Luciano Lingnau [Paessler Support]


Dec, 2017 - Permalink

Hello, Luciano Lingnau.

Finishing the configuration process for the integrated PRTG installation to open a ticket in the CA SDM tool, however I am getting an error: No response (code: PE002)

Would you help me.


Jul, 2018 - Permalink

Is the PRTG Server actually able to reach the URL given in the notification?

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink

Hi, Stephan Linke, Yes, telnet and ping are happening successfully. Any other tips to help me?


Aug, 2018 - Permalink

Sorry, that was perhaps ambiguously put - I was actually talking about the URL you're trying to use with PRTG. When opening it within a browser on the PRTG server, does the case in CASDM actually get closed?

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink