PagerDuty
Setting up PagerDuty
The Events API integration, routing keys and escalation contacts for PagerDuty.
Before you start
Decide which services should receive escalations and who owns each one. A routing key per service keeps payment issues, fraud reports and channel outages with the teams that can act on them.
Steps
Each channel installs disabled, so nothing is sent before these steps are done.
Add the integration
Add an Events API integration to the default service and copy its routing key.
Store the key
Enter the routing key in the PagerDuty Events credential.
Set severity and source
Choose them per environment in the Reach settings.
Create escalation contacts
Create one contact per service, with its routing key as the PagerDuty identity.
Enable the channel
Register the channel as enabled and send a test escalation from staging.
PagerDuty is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.