- Essentials
- In The App
- Infrastructure
- Application Performance
- Log Management
- Security Platform
- UX Monitoring
- Administration
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 appears in your Event Stream
The PagerDuty integration does not include any service checks.
To resolve a PagerDuty service automatically when a monitor recovers, include the PagerDuty notification in the {{#is_recovery}}
context of your Say what’s happening section of your monitor as follows:
{{#is_recovery}}
This notification will only occur if the monitor resolves.
If @pagerduty-trigger was triggered for the alert, it'll be resolved as well
{{/is_recovery}}
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.
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.