Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana/v10.3/alerting/alerting-rules/manage-contact-points/integrations/pager-duty.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana/v10.3/alerting/alerting-rules/manage-contact-points/integrations/pager-duty/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Configure PagerDuty for Alerting
To set up PagerDuty, provide an integration key.
| Setting | Description |
|---|---|
| Integration Key | Integration key for PagerDuty |
| Severity | Level for dynamic notifications, default is critical |
| Custom Details | Additional details about the event |
The CustomDetails field is an object containing arbitrary key-value pairs. The user-defined details are merged with the ones we use by default.
Our default values for CustomDetails are:
{
"firing": `{{ template "__text_alert_list" .Alerts.Firing }}`,
"resolved": `{{ template "__text_alert_list" .Alerts.Resolved }}`,
"num_firing": `{{ .Alerts.Firing | len }}`,
"num_resolved": `{{ .Alerts.Resolved | len }}`,
}In case of duplicate keys, the user-defined details overwrite the default ones.