PagerDuty Integration

Connect your StatusPage.me monitors and incidents to PagerDuty for automatic incident management. When a monitor goes down or an incident is created, a PagerDuty incident is triggered. When the issue resolves, the PagerDuty incident is automatically resolved.

What is PagerDuty?

PagerDuty is an incident management platform that helps teams detect and respond to operational issues. By integrating it with StatusPage.me, your on-call team is automatically alerted through PagerDuty’s escalation policies when something goes wrong.

Prerequisites

• A PagerDuty account (any paid plan)
• A StatusPage.me account on a paid plan or OSS Hero
• A PagerDuty Service where incidents should be created

Setup Steps

1. Create an Events API v2 Integration in PagerDuty

1. Log in to your PagerDuty account
2. Go to Services and select (or create) the service you want to receive alerts
3. Click the Integrations tab
4. Click Add an integration
5. Search for and select Events API v2
6. Click Add
7. Copy the Integration Key (also called Routing Key) - you’ll need this in the next step

2. Add PagerDuty Channel in StatusPage.me

1. Go to /user/status-pages/notifications
2. Click Add Channel
3. Select PagerDuty
4. Enter a friendly name (e.g., “PagerDuty - Production”)
5. Paste the Integration Key from step 1
6. Click Save Channel

3. Link to a Status Page

1. Open your status page settings: /user/status-pages/{status_page_id}/settings#notifications
2. Click Link Channel
3. Select your PagerDuty channel and link it
4. Toggle it on

4. Test the Integration

1. Go back to /user/status-pages/notifications
2. Click Test next to your PagerDuty channel
3. Check PagerDuty - you should see a test incident created on your service

How Events Map to PagerDuty

StatusPage.me automatically maps events to PagerDuty actions:

Auto-Resolution

StatusPage.me uses dedup keys to link trigger and resolve events. When a monitor goes down, a PagerDuty incident is triggered with a unique key. When the same monitor recovers, a resolve event is sent with the same key, automatically closing the PagerDuty incident.

Plan Availability

PagerDuty notifications are available on:

• Pro, Growth, Business, and Enterprise plans
• OSS Hero plan

PagerDuty is not available on the Free plan.

Troubleshooting

Test notification fails

• Verify the Integration Key is correct (32-character hex string)
• Ensure the PagerDuty service is not disabled
• Check that the integration type is Events API v2 (not v1)

Incidents not auto-resolving

• Auto-resolution relies on matching dedup keys. Ensure both the trigger and resolve events come from the same StatusPage.me channel
• Check PagerDuty’s incident timeline for the dedup key

Duplicate incidents

• Each monitor/incident generates a unique dedup key, so duplicate triggers for the same event should be suppressed by PagerDuty
• If you see duplicates, check whether you have multiple PagerDuty channels linked to the same status page

What’s Next?

• Notification Channels Overview
• Notification Hub guide
• Set up your first monitor