Statusfield Logo
StatusfieldDocs

Integrations

PagerDuty

Trigger and auto-resolve PagerDuty incidents when monitored services go down

Route Statusfield alerts straight into your PagerDuty on-call rotation. When a monitored service degrades, Statusfield opens a PagerDuty incident; when it recovers, the incident resolves itself automatically — no manual clean-up.

Plan Availability

PagerDuty is available on higher-tier plans. See the pricing page for current availability, or open the PagerDuty card on your integrations page to check whether it's included in your plan.

How It Works

Statusfield uses PagerDuty's Events API V2. Each monitored service maps to a single PagerDuty incident:

  • Degradation triggers an incident — the incident summary names the service and its new status.
  • Recovery resolves it automatically — when the service returns to Operational, Statusfield resolves the same incident.
  • One incident per service — if several components of the same service change, they update the existing incident instead of paging you again for each one.
  • Severity is derived from status — outages map to higher PagerDuty severities (critical / error), lesser issues to warning.

No Alert Fatigue

Because incidents are keyed per service, a flapping service won't spam your on-call. You get one incident that stays open until the service actually recovers.

Quick Start

1

Create an Events API V2 Integration in PagerDuty

In your PagerDuty account:

  1. Open the Service you want alerts on (or create one)
  2. Go to the Integrations tab → Add integration
  3. Choose Events API V2
  4. Copy the generated Integration Key (also called the routing key) — it's a 32-character string

Where the incident lands

The PagerDuty Service you attach the integration to determines which escalation policy and on-call schedule handle the alert. Pick the Service whose responders should react to this outage.

2

Add the Integration to Statusfield

  1. Go to statusfield.com/integrations
  2. Click the PagerDuty card
  3. Give it a Name (e.g., "On-call escalation")
  4. Paste your Routing Key (Integration Key)
  5. Click Create
3

Test It Out

  1. Click the menu (⋮) next to your PagerDuty integration
  2. Select Test Notification
  3. A test incident appears in PagerDuty and then resolves itself moments later — confirming the routing key works end to end
4

Configure Notifications

When adding a monitor for a service:

  1. Go to statusfield.com/notifications
  2. Find the service in the list
  3. Choose which status changes should page you (any change, degraded, partial outage, major outage, maintenance)

Every configured status also resolves the incident when the component returns to Operational.

Incident Format

Each PagerDuty incident Statusfield opens includes:

  • Summary — the service name and its new status (e.g., "GitHub: Major Outage")
  • Source — statusfield.com
  • Severity — mapped from the service status (critical, error, warning, or info)
  • Dedup key — scoped to the service, so updates and the recovery land on the same incident

Troubleshooting

Not Receiving PagerDuty Incidents?

Common issues and solutions:

1. Invalid routing key

  • The routing key must be the Integration Key from an Events API V2 integration (32 characters). Keys from other integration types won't work.
  • Re-copy the key from PagerDuty and update the integration in Statusfield.

2. Incident opened but nobody was paged

  • Check the escalation policy on the PagerDuty Service you attached the integration to — the on-call schedule there controls who gets notified.

3. Incident didn't resolve

  • Resolution fires when the service returns to Operational. A service that stays degraded keeps its incident open by design.

Security & Privacy

  • Routing keys are stored encrypted in our database.
  • Statusfield only sends incident triggers and resolves — it never reads your PagerDuty incidents, schedules, or user data.
  • All PagerDuty API calls use HTTPS.

Need Help?

Contact our support team at support@statusfield.com