Overview

PagerDuty is an incident management platform that equips IT teams with immediate incident visibility, enabling proactive and effective responses to maintain operational stability and resilience.

PagerDuty incidents can be configured as a data source for failures in DORA Metrics.

Setup

To integrate your PagerDuty account with DORA Metrics, navigate to Integrations > Developer Tools in PagerDuty and click Generic Webhooks (v3).

1. Click + New Webhook and enter the following details:

   Variable	Description
   Webhook URL	Add https://webhook-intake./api/v2/webhook/.
   Scope Type	Select Account to send incidents for all PagerDuty services in your account. Alternatively, you can send incidents for specific services or teams by selecting a different scope type.
   Description	A description helps distinguish the webhook. Add something like Datadog DORA Metrics integration.
   Event Subscription	Select the following events: -incident.acknowledged -incident.annotated -incident.custom_field_values.updated -incident.delegated -incident.escalated -incident.priority_updated -incident.reassigned -incident.reopened -incident.resolved -incident.triggered -incident.unacknowledged
   Custom Headers	Click Add custom header, enter DD-API-KEY as the name, and input your Datadog API key as the value. Optionally, you can add an environment to all of the PagerDuty incidents sent from the webhook by creating an additional custom header with the name dd_env and the desired environment as the value.

2. To save the webhook, click Add Webhook.

The severity of the incident in the DORA Metrics product is based on the incident priority in PagerDuty.

Note: Upon webhook creation, a new secret is created and used to sign all the webhook payloads. That secret is not needed for the integration to work, as the authentication is performed using the API key instead.

Mapping PagerDuty services to Datadog services

When an incident event is received for a specific PagerDuty service, Datadog attempts to retrieve the related Datadog service and team from the Service Catalog.

The matching algorithm works in the following scenarios:

1. If the incident service URL matches with the PagerDuty service URL configured for one or more services in the Service Catalog:
   • If the incident service URL matches a single Datadog service, the incident metrics and events are emitted with the Datadog service name and team retrieved from the Service Catalog.
   • If the incident service URL matches multiple Datadog services, the incident metrics and events are emitted with the Datadog team name.

For more information about setting the PagerDuty service URL for a Datadog service, see Use Integrations with Service Catalog.

2. If the PagerDuty service name of the incident matches a Datadog service name in the Service Catalog, the incident metrics and events are emitted with the Datadog service name and team retrieved from the Service Catalog.
3. If the PagerDuty team name of the incident matches a Datadog team name in the Service Catalog, the incident metrics and events are emitted with the corresponding Datadog team name.
4. If the PagerDuty service name of the incident matches a Datadog team name in the Service Catalog, the incident metrics and events are emitted with the Datadog team name.

Further Reading

Documentation, liens et articles supplémentaires utiles:

See other incident data source optionsDOCUMENTATION Learn about setting up deployments in DORA MetricsDOCUMENTATION Learn about Event ManagementDOCUMENTATION Learn about Metric MonitorsDOCUMENTATION Check out the latest Software Delivery releases! (App login required)RELEASE NOTES