PRTG Integration Guide for Network Monitoring Alerts

Pointers

• The integration is between a TaskCall service and PRTG.
• Incidents will automatically resolve in TaskCall when metrics fall back within the normal threshold.
• This integration only receives alerts in TaskCall from PRTG.

In TaskCall

1. Go to Configurations > Integrations and click New Integration.
2. Select the PRTG integration.
3. Give the integration a name and configure how incidents will be created. Only the Default Service field is required. The rest are optional.
4. Incidents (Optional)
   1. TaskCall automatically maps incoming payloads with internal attributes to create incidents. However, this can be customized in the Incidents tab. Constant values can be included alongside placeholders to dictate which attributes should map to the Incident Title, Description, Tags, Snapshots and Vendor URL. To insert a placeholder use double curly braces.
      
      
      
      For example, if you enter {{ alert.title }} in the Incident Title field, TaskCall will look for an attribute called "title" nested inside another attribute called "alert" in the incoming payload. If the nested attribute exists, its corresponding value will be pulled from the payload and inserted. If the nested attribute does not resolve successfully, TaskCall will fall back to the default mapping.
      
      If you are unsure, please leave the fields empty. TaskCall will use the default mapping to create the incident for you.
   2. Select the Urgency level the incident should be created at.
   3. Select the option to Group similar alerts together if you would like follow up triggers from the same alert source to be grouped into the same incident. If you leave this option unchecked, then a new incident will be created for every trigger. (This behavior is specific to new triggers; not updates to an alert.)
   4. Click Next to move on to the Services tab.
5. Services (Required)
   1. Select the Default Service incidents should be sent to. To route incidents to different services instead, set Map With Attribute to the attribute to route by using a placeholder. Then, map each value it can take to the service that should receive it.
      
      For example, to route by a region attribute sent in the payload, set Map With Attribute to {{ region }}, then map US to one service and EU to another, and so on.
      
      
   2. Click Next to move on to the Authorization tab.
6. Authorization (Optional)
   1. The Authorization tab allows a Bearer Token and an IP Allowlist be added if you would like to restrict who is able to send alerts to this integration. If you are unsure, this can be skipped.
7. Once done, click Save.
8. Copy the Integration Url that is issued for the integration. This will be used to set up the notification in PRTG.

In PRTG

1. Go to Setup > Account Settings > Notification Templates.
   
   
   
   
2. Hover over the "+" sign on top right side and click Add Notification Template.
   
   
   
   
3. Give the template a name and for the Notification Summarization select Always notify ASAP, never summarize.
   
   
   
   
4. Scroll down to the Execute HTTP Action section. Paste the integration url you copied over from TaskCall in the URL field. Select POST as the HTTP Method.
   
   
   
   
5. Copy and paste the below payload in the Payload field. Ensure that there are no spaces in between the words and lines in the payload. Then click Create.
   
   
   
   
   colorofstate=%colorofstate&company=%company&comments=%comments&commentssensor=%commentssensor&commentsdevice=%commentsdevice&commentsgroup=%commentsgroup&commentsprobe=%commentsprobe&coverage=%coverage&cumsince=%cumsince&date=%date&datetime=%datetime&device=%device&deviceid=%deviceid&down=%down&downtime=%downtime&elapsed_lastcheck=%elapsed_lastcheck&elapsed_lastdown=%elapsed_lastdown&elapsed_lastup=%elapsed_lastup&group=%group&groupid=%groupid&history=%history&home=%home&host=%host&iconofstate=%iconofstate&lastcheck=%lastcheck&lastdown=%lastdown&lastmessage=%lastmessage&laststatus=%laststatus&lastup=%lastup& lastvalue=%lastvalue&linkprobe=%linkprobe&linkgroup=%linkgroup&linkdevice=%linkdevice&linksensor=%linksensor&location=%location&message=%message&name=%name&nodename=%nodename&objecttags=%objecttags&parenttags=%parenttags&priority=%priority&probe=%probe&probeid=%probeid&programname=%programname&sensor=%sensor&sensorid=%sensorid&server=%server&serviceurl=%serviceurl&settings=%settings&shortname=%shortname&since=%since&sitename=%sitename&statesince=%statesince&status=%status&systemdatetime=%systemdatetime&tags=%tags&time=%time&timezone=%timezone&uptime=%uptime
   
   
   
   
   
6. Once the notification template has been created, you can use it in triggers to send alerts to TaskCall. To do so, go to Devices > All > Notification Triggers.
7. Click the "+" button on the top right side and select the type of trigger you want to create. There are several types of triggers that PRTG allows you to create. In this example we will add a State Trigger. This will go off when the state of a sensor changes.
   
   
   
   
8. Select the parameters you want for the trigger and choose to perform the TaskCall notification template you created earlier. Click the blue tick button on the left side to save it.
   
   
   
   
9. Done! You have fully completed the integration between TaskCall and your PRTG monitoring tool. You can test the integration by running simulations on the sensors.