Connect PagerDuty

Before you begin

• Access to the PagerDuty service that should receive the events.
• Owner or admin permission in the GetPulseCheck account.

Add the integration

1. In PagerDuty, open the target service and its Integrations tab.
2. Add an Events API V2 integration and copy its integration key. GetPulseCheck calls this value the routing key.
3. In GetPulseCheck, open Account Settings and find the PagerDuty Integration section.
4. Paste the routing key and select Save routing key.

Routing key and security rules

• The routing key must be 32 to 255 characters after trimming.
• It cannot contain whitespace.
• GetPulseCheck encrypts the key at rest and shows only its last four characters after saving.
• Only account owners and admins can save or disconnect the integration.

Test the connection

1. Return to the PagerDuty Integration section after saving the routing key.
2. Select Send test alert.
3. Confirm the test incident in PagerDuty. It uses the summary GetPulseCheck Test Alert, source getpulsecheck.io, and info severity.
4. Check the updated Last tested time in GetPulseCheck.

How PagerDuty matches recovery

Each live PagerDuty event uses the GetPulseCheck incident ID as its deduplication key. The recovery event reuses that same key, so PagerDuty resolves the alert that belongs to the incident. A later outage on the same monitor receives a new incident ID and remains a separate PagerDuty incident.

Related

• How alerting works
• Testing alerts and recovery