Connect PagerDuty to Datadog in order to:
@pagerduty in your postSee the Datadog Integration Guide from Pagerduty.
Once you have Pagerduty integrated, you can check out Datadog’s custom Pagerduty Incident Trends.
The PagerDuty integration does not include any metrics.
Your PagerDuty Triggered/Resolved events appear in the Events Explorer.
The PagerDuty integration does not include any service checks.
To send a message or notification to a specific PagerDuty service when multiple services are integrated, use @pagerduty-[serviceName] in your monitor message. If you start typing it in your monitor Say what’s happening section, you should see it autocomplete.
When a monitor recovers, it automatically resolves the Pagerduty service if you include the notification handle in the monitor recover message but won’t if it’s only included in the{{#is_alert}} context.
The severity of PagerDuty incidents is determined by the status of the monitor that is causing the alert. The following table illustrates how the alert status is mapped to a PagerDuty incident severity.
| Monitor status | PagerDuty incident severity |
|---|---|
ALERT | error |
NODATA | error |
WARNING | warning |
OK or others | info |
For example, if the monitor transitions from OK to WARNING and notifies a @pagerduty-[serviceName], the created PagerDuty incident will be of severity warning.
Note: This mapping happens automatically, and cannot be modified.
Datadog has an upper limit on your monitor notification lengths sent to PagerDuty. The limit is at 1024 characters.
Additional helpful documentation, links, and articles:
