PagerDuty
PagerDuty empowers users and organizations to prevent and resolve business-impacting incidents for exceptional customer experience. PagerDuty helps organizations with the insight to proactively manage events that may impact customers across their IT environment.
When you select PagerDuty as service destination, any subscribed notification about an event can be sent as an alert to PagerDuty channels.
Generate PagerDuty routing key
To integrate your PagerDuty service to Event Notifications service destination, you need to generate a PagerDuty routing key. To generate a PagerDuty routing key, follow these steps: Generate a new Integration Key.
If you already integrated EventsV2 API with your PagerDuty service, go to the service directory, select More, and select View Integrations. The Integration key is available in this view.
Configuring a PagerDuty destination
You can configure a PagerDuty destination in the Destinations tab.
To configure a PagerDuty destination, complete the following steps:
-
From your Event Notifications instance, click Destinations.
-
Click Create to create a new destination.
-
Enter the following destination details in the Create destination dialog:
- Name: Enter a name for your destination.
- Description: Optionally, enter a description for your destination.
- Type: Under Destination, select PagerDuty from the dropdown list as your destination type.
- Routing key: Enter the routing key generated earlier.
-
Click Create destination.
PagerDuty alert events supported by Event Notifications
Event Notifications supports only alert events of PagerDuty. For more information, see Send an alert event.
| Event Notifications field | PagerDuty field | Supported |
|---|---|---|
routing_key (Destination Config) |
routing_key |
Yes |
trigger (default) |
event_action |
Partial |
ibmendefaultlong |
payload.summary |
Yes |
critical - HIGH, error - MEDIUM, warning - LOW, info - INFO, Default Severity - LOW |
payload.severity |
Yes |
time (cloud events) |
payload.timestamp |
Yes |
data |
payload.custom_details |
Yes |
source |
payload.source |
Yes |
| NA | dedup_key |
No |
| NA | payload.component |
No |
| NA | payload.group |
No |
| NA | payload.class |
No |
| NA | images |
No |
| NA | links |
No |
| Event Notifications severity | PagerDuty severity |
|---|---|
| Critical | Critical |
| High | Error |
| Medium | Warning |
| Low | Info |
| Anything Else | Info |
Testing a PagerDuty destination configuration
You can test a PagerDuty destination in the options menu next to the destination. You can test whether the provided configuration is correct with a single click.
For more information on testing a destination, see Testing Destinations.
PagerDuty retry policy
When sending notifications to PagerDuty, issues such as network errors and application glitches can cause the requests to fail. Event Notifications automatically retries failed requests to provide resiliency.
For detailed information about retry behavior, including retry attempts, delays, and timeout values, see Retry policy for destinations.