Start Using PagerDuty Today
Try PagerDuty free for 14 days — no credit card required.
PRTG is a central component of networking monitoring. It is used to monitor the state, health, and performance of everything from servers to networking devices.
Alerts generated in PRTG can trigger incidents in PagerDuty, to alert the appropriate technician via SMS, phone, email or push. The guide below describes how to integrate your PRTG installation with PagerDuty
PRTG Network Monitor can trigger and resolve PagerDuty incidents via email. Below are the steps that are required to setup the communication between PRTG and PagerDuty.
1. Open PRTG Enterprise Console from your server’s desktop.
2. Selecg the Setup tab from the Enterprise Console.
3. From the sidebar menu, select Notifications, then click the + Add new notification button.
4. Configure the notification settings:
– Enter a Notification Name (example shows “PagerDuty Notification”).
– In the Notification Summarization section, select the Always notify ASAP option.
– Check the Send Email checkbox.
– In the Send to Email Address field, enter the PagerDuty integration key email address (from In PagerDuty, steps 4 and 6 above).
– Default Subject and Message formats are set, but can be customized to fit your needs.
– Click Save.
5. Setting triggers: This can be done in several ways to fit your needs. For this method we will be using a Parent Trigger which will propagate to the lower children in the class. Select the Devices tab and highlight the Parent PRTG Server Connections. Select the Notifications tab, and click the + Add State Trigger button.
6. Here you will configure the details to define your trigger. In this example, a PagerDuty notification will trigger when sensor state is Warning for at least 0 seconds. You can also add a repeat function if the sensor is down for X amount of seconds to perform the PagerDuty Notification action again. Then select the option to alert the PagerDuty Notification when the condition clears.
6. Select the Notifications tab and ensure Inherit all triggers from parent objects and use the triggers defined below is selected.
This completes the PRTG configuration. Continue below to set the Auto-Resolve functionality in PagerDuty.
Per your PRTG instance there are several emails that can be sent to PagerDuty depending on what sensor has the failure/warning . In this example we are going to ‘Trigger‘ an incident based off of the ‘Threshold reached‘, ‘Down’ and ‘Warning’ states and ‘Resolve‘ an incident based off of the ‘Down Ended‘, ‘Up‘ and ‘Threshold not reached‘ states.
To enable this option you will need to make the following changes to your PagerDuty PRTG Email Service:
1. In PagerDuty, go to Services, and click Service Directory.
2. Find and click the service for your PRTG integration, select the Integrations tab and click the cog icon to the right of the email integration.
3. At the top right, click the Edit Integration button.
4. Under Email Management, select the option Open and resolve incidents based on custom rules.
5. Create a resolve rule. Set the rules as follows:
– resolve
an incident if any
of the following conditions apply:
– The email subject
contains Down Ended
– The email subject
contains Up
– The email subject
contains Threshold not reached
– Link incoming emails to the same incident if they share this key:
– In the email body
, match this regular expression
Sensor.([a-zA-Z.0-9\s]+)
6. Create a trigger rule. Set the rules as follows:
– trigger
an incident if any
of the following conditions apply:
– The email subject
contains Down
– The email subject
contains Threshold reached
– The email subject
contains Warning
– Link incoming emails to the same incident if they share this key:
– In the email body
, match this regular expression
Sensor.([a-zA-Z.0-9\s]+)
7. Under the newly created rules, set the final catch-all rule to: If an email does not match any of the rules above, discard it
8. Click the Save changes button.
Your PRTG Integration with PagerDuty is now be complete. When an alert populates in PRTG, you will now receive a notification in PagerDuty.
Yes. This will need to be configured within your PagerDuty PRTG Email service, with the detailed steps listed above.
Yes, you will need to create multiple PRTG Email Services, then create the additional Contacts within your PRTG server.
Yes, Incidents are de-duplicated, The incident key is returned for the initial alert that creates the incident.
No.
Yes, all alerts are stored and displayed for users within the ‘Logs’ tab in your PRTG UI.
Yes, this is configured in the ‘trigger‘ for each instance or parent.
Try PagerDuty free for 14 days — no credit card required.