apitech
/
grafana
mirror of https://github.com/grafana/grafana
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
48977 Commits
586 Branches
650 Tags
2.3 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 2b4f108771
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2b4f108771'
${ noResults }
grafana/docs/sources/alerting/alerting-rules/manage-contact-points/integrations/pager-duty.md

1.3 KiB
Raw Blame History

canonical description keywords labels menuTitle title weight
https://grafana.com/docs/grafana/latest/alerting/alerting-rules/manage-contact-points/integrations/pager-duty/ Configure the PagerDuty integration for Alerting [grafana alerting pagerduty] [{products [cloud enterprise oss]}] PagerDuty Configure PagerDuty for Alerting 400

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.