Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
PagerDuty’s alerting platform allows users to centrally manage incidents with alerting, on-call scheduling, escalation policies, and incident tracking intended to increase the reliability and performance of your systems. Your LogicMonitor account comes pre-configured to integrate with your PagerDuty account. The integration enables LogicMonitor to open, update and close PagerDuty incidents and/or alerts based on LogicMonitor alerts. By sending alerts from LogicMonitor into PagerDuty, you can take advantage of PagerDuty’s alerting platform features to increase uptime of your apps, servers, websites, and databases. As with all integrations, LogicMonitor extends or provides functionality without impacting the other solutions you have implemented.
Note: As of v.116 (released in March of 2019), LogicMonitor’s PagerDuty integration supports V2 of PagerDuty’s Events and Webhook APIs. If you would like to upgrade an integration configured in an earlier release of LogicMonitor, see the Upgrading an Existing V1 PagerDuty Integration section of this support article for instructions.
You can use the LogicMonitor PagerDuty integration to create, update and close PagerDuty incidents in response to alerts triggered in your account. You’ll need to perform the following primary steps to set up PagerDuty integration.
When a triggered alert matches the alert rule and is routed to the escalation chain with the PagerDuty integration, an incident will be created in your
PagerDuty account. The ticket can then be updated and/or closed when the alert is acknowledged, escalated, de-escalated and/or cleared.
You will need to set up a new service in PagerDuty (Services | Add Service). As shown next, select “LogicMonitor” from the Integration Type field’s dropdown menu.
The option found under the Incident Behavior heading can be set to either Create alerts and incidents or Create incidents. To use PagerDuty’s event grouping, leave the default Create alerts and incidents option selected.
A new integration key will be generated once you add the service. You will need to save the key for later use when setting up the PagerDuty integration in your LogicMonitor account.
To begin configuring your PagerDuty integration in LogicMonitor, navigate to Settings | Integrations | Add | PagerDuty. As shown (and discussed) next, there are several settings that must be established in order to configure PagerDuty integration.
In the Integration Key field, enter the PagerDuty integration key retrieved in the previous section.
The HTTP Delivery section controls how LogicMonitor formats and sends the HTTP Post requests to create, update and/or close incidents. By default, LogicMonitor will pre-populate four different HTTP requests, one for each of the following alert statuses:
For each request, you can select which alert statuses should trigger the HTTP request. Requests will be sent for new alerts (status: Active), and can additionally be sent for alert acknowledgements (status: Acknowledged), clears (status: Cleared) and escalations/de-escalations (status: Escalated). Note that each alert status can only be associated with one request. Since LogicMonitor auto-populates a different request for each alert status by default, you’ll have to delete a request in order to see the option to include that alert status in a different request.
You shouldn’t need to edit anything in the HTTP Delivery section, but if you wish to create a customization of some kind, use the information in the following sections to guide you. If no customizations are required, save the integration and add it to an escalation chain, as discussed in Escalation Chains.
The HTTP method for PagerDuty integrations is restricted to POST.
The URL field displays the URL that the HTTP request should be made to. This field is auto-populated based on information you’ve provided.
The text block found under the Alert Data heading displays custom formatted alert data to be sent in the HTTP POST request (used to create, update and close PagerDuty incidents). This text will be auto-populated for you. If desired, you can customize the alert data field using tokens.
Check the Include an ID provided in HTTP response when updating alert status option if you’d like LogicMonitor to find the PagerDuty incident ID returned in the response to the HTTP request associated with a new alert, and use the ID in any subsequent requests for alert acknowledgements, clears and escalations/de-escalations. By default, this option will be selected.
If LogicMonitor is to use the ID provided in the response, select the format the response will be in from the HTTP Response Format field’s dropdown.
Clicking the Test Alert Delivery button sends a test alert and provides the response, allowing you to test whether you’ve configured the integration correctly.
Alert rules and escalation chains are used to deliver alert data to your PagerDuty integration. When configuring these, there a few guidelines to follow to ensure incidents are opened, updated, and closed as expected within PagerDuty. These guidelines are discussed in Alert Integrations Overview.
You can acknowledge LogicMonitor alerts directly from the PagerDuty platform. To set up this functionality, you will need to establish a LogicMonitor extension (i.e. webhook) within PagerDuty using the following steps.
Note: If you are upgrading from V1 to V2, as discussed in the Upgrading an Existing V1 PagerDuty Integration section of this support article, a prompt will warn you that you are overwriting the previous token. This is okay; click the Generate button to proceed with generating the token.
For your convenience, LogicMonitor has automated the process of updating payloads from PagerDuty’s V1 APIs to V2. Simply open your PagerDuty integration in LogicMonitor and, from the Manage Integration dialog, click the Upgrade Payload to v2 button.
Your previously configured PagerDuty service will continue to work without updates. However, if you would like to have the LogicMonitor integration use PagerDuty’s Event Intelligence capabilities, follow these steps in PagerDuty to update the service:
If your PagerDuty service is currently using the “Generic Webhook V1” extension to acknowledge LogicMonitor alerts from PagerDuty, you’ll need to update the extension to continue to successfully acknowledge events.
The following tokens are available:
In This Article