Skip to main content
A PagerDuty destination sends Squasher incidents to a PagerDuty service through the Events API v2. One Squasher incident stays one PagerDuty alert from trigger to resolve. To send alerts the other way, from a tool into Squasher, see PagerDuty Events API v2 inbound.

​
What you need

  • A PagerDuty service, and permission to add an integration to it.
  • The owner, admin, or security admin role in the Squasher organization.

​
Connect a PagerDuty service

1

Get an integration key in PagerDuty

Open the service in PagerDuty, add an integration of the type Events API V2, and copy its integration key.
2

Add the destination in Squasher

  1. Open your project and select Settings in the sidebar, then the Notifications tab. 2. Under Add destination, choose PagerDuty in Channel, and enter a Name. 3. Paste the key in PagerDuty integration key, then select Add destination.
3

Choose which incidents page

Squasher adds the destination to the default route, which sends every incident. To page only for some incidents, for example sev-1, add a route with a severity filter. See Add a route with filters.
Send test sends a real trigger event, so it opens an alert in PagerDuty. Resolve that alert in PagerDuty after the test.

​
What Squasher sends

The dedup_key is the Squasher incident ID, so PagerDuty keeps every event of one incident on one alert. The severity comes from the rank of the incident severity: To map severities another way, create the destination with the Notifications API and set severityMap, for example { "sev-1": "critical", "sev-2": "critical" }. The dashboard has no field for it.

​
Limits

  • Squasher shows only the last four characters of the key after you save it. You cannot edit a destination: to change the key, remove the destination and add it again.
  • A route without an event filter sends only opened and resolved. Add acknowledged to the route’s events to acknowledge alerts in PagerDuty too.
  • Acknowledging or resolving the alert in PagerDuty does not change the Squasher incident.

​
Move schedules from PagerDuty

Squasher has no importer for PagerDuty schedules. To move a rotation to Squasher on-call, create a Squasher schedule with the same members in the same order, handoff day, and time. Check squasher on-call who-is-on against PagerDuty before you change your routes.

​
Next steps

Notifications

Routes, events, and delivery rules for every destination.

On-call

Run rotations in Squasher.