Use PagerDuty as an alert receiver
You can configure Amazon Managed Service for Prometheus to send alerts directly to PagerDuty. This integration requires you to store your PagerDuty integration key in AWS Secrets Manager and grant Amazon Managed Service for Prometheus permission to read the secret.
PagerDuty integration enables automated incident response workflows and ensures
critical alerts reach the right team members at the right time. When you use
PagerDuty as an alert receiver, you can take advantage of PagerDuty's escalation
policies, on-call scheduling, and incident management features to ensure that alerts
are acknowledged and resolved quickly. This integration is particularly valuable for
production environments where rapid response to system issues is essential for
maintaining service availability and meeting SLA requirements. For more information,
see PagerDuty Knowledge Base
PagerDuty configuration options
| Option | Description | Required |
|---|---|---|
|
|
The PagerDuty routing key for an integration on a service. You must specify this as an Secrets Manager ARN |
Yes |
|
|
The PagerDuty service key for an integration on a service. You must specify this as an Secrets Manager ARN |
Yes (for Events API v1) |
|
|
The client identification of the notifier |
No |
|
|
A backlink to the sender of the notification |
No |
|
|
Description of the incident |
No |
|
|
A set of arbitrary key/value pairs that provide further detail about the incident |
No |
|
|
Severity of the incident |
No |
|
|
The class, or type, of the event |
No |
|
|
Component of the source machine that is responsible for the event |
No |
|
|
Logical grouping of components |
No |
|
|
The unique location of the affected system |
No |
Note
The url, service_key_file,
routing_key_file, and http_config options are
not supported.
The following topics describe how to configure PagerDuty as an alert receiver in Amazon Managed Service for Prometheus.
Topics
