Integrating PagerDuty with OpManager (using Webhook)

OpManager is an easy-to-use and affordable network monitoring tool that monitors network devices of all kinds such as routers, switches, storage devices, VMs, firewalls and more for performance and availability.

You can configure webhook integration in OpManager to collaborate with other third party applications and enhance its fault resolution capabilities to reduce mean time to repair and maximize network uptime.

PagerDuty

PagerDuty is an alarm aggregation and incident response solution, and helps you view the alerts and messages from a network monitoring tool in a single console and manage them appropriately so that the network issues are resolved much quicker.

Alerts from your monitoirng tool will be logged as incidents in PagerDuty, where you can customize the mode of communication for each type of incident. 

For example, you can choose to escalate a low severity incident via an email while on the other hand, configure to receive a phone call for a critical incident that posses as serious threat to your network.

How OpManager-PagerDuty integration leverages network monitoring

OpManager generates alarms for device unavailability, threshold violations and any kind of network faults. By integrating OpManager with PagerDuty you can relay the details of the alarms in PagerDuty and configure to receive notifications.

PagerDuty allows you to customize the type of notification received based on the severity of the alert. For example, you can configure to receive critical alerts via a phone call and on the other hand receive attention alerts via an SMS or an email.

This way you can prioritize the issues and resolve them accordingly to ensure that all the network issues are sorted quickly.

How to integrate OpManager with PagerDuty

Note: OpManager-PagerDuty integration can be implemented via webhooks.

The integration process involves two parts.

• Service Integration configuration in PagerDuty
• Webhook configuration in OpManager

Steps to executed in PagerDuty

Integration Type: OpManager-PagerDuty integration is established through Events API V2.

1. In your PagerDuty instance, go to Services → Service Directory.
2. Next to the service you wish to integrate with, click More and select View Integrations.
3. Click on Add Integration, select Events API V2 and click "Add".
4. Copy the Integration Key and the URL for Alert Events from the next window.

Steps to be executed in OpManager

Stage 2 (Invoking a webhook)

Select Invoke a Webhook and add the following details:

1. Method: POST
2. URL: https://events.pagerduty.com/v2/enqueue (The Events URL copied from PagerDuty)
3. Data Type: raw
4. Payload Type: JSON
5. Body content: In this field, the "$message" and "$DeviceField(ipAddress)" are default message variables available in OpManager. You can use any of these variables in the body of the message by clicking on the '+' icon next to the Body Content field.

   {
"event_action": "trigger",
"routing_key":"insert_integration_key_here",
"payload": {
"summary": "$message",
"severity":"critical",
"source":"$DeviceField(ipAddress)"
}
}

6. Timeout (in seconds): Any value between 1 and 300.

Note: When you use a $ variable, it takes the relevant information from the alert and displays it in the message you receive. For example, when you use $message in the Body Content field, the exact alarm message will be replaced for the variable used. Similarly, for all $ variables the exact value will be displayed in the message you receive. 

Stage 3

1. Once you have configured all these details, click Next.
2. In the following window, configure the trigger criteria for the webhook. You can configure alerts raised from any of the monitors to act as the trigger. Once done, click Next.
3. Configure the devices that you wish to apply this profile. Only alerts raised from the selected devices will be forwarded to PagerDuty. Select the applicable devices, move them to the Selected Devices window using the right arrow and click Next.
4. Finally, configure the Time Window/Delayed Trigger/Recurring Trigger options, click Next to add a name to this profile and click "Save" to enable the integration.
5. Before saving it, make sure to use the Test Action option to check if the integration has been configured properly. Note that the message variables used in the body of the request will not have any value when Test Action is performed, and will only send the content as such.

The configuration enables OpManager to send alerts to PagerDuty which will be stored as incidents.

For more details, you can also refer to the PagerDuty Events API V2 help article.