Skip to content
Statusfield LogoStatusfield

Integrations

PagerDuty

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

On this page

Route selected Statusfield status changes into PagerDuty for your on-call team. A matching rule sends a trigger event; a detected return to Operational sends a resolve event. Keep the destination and alert rule active so recovery can reach PagerDuty.

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 to send status changes that match your notification rules:

  • Selected problem states trigger an incident: the summary names the service and its new status.
  • Recovery sends a resolve event: when the monitored service returns to Operational, Statusfield sends a resolution for the matching incident.
  • Related updates share an incident key: vendor component changes use the same service key. Regional endpoint checks use separate keys so recovery in one location does not resolve another location’s incident.
  • Severity follows status: outages map to higher PagerDuty severities (critical / error), lesser issues to warning.

Choose what should page you

Select the problem states that need an on-call response. Repeated updates with the same key can update an open incident. A new failure after recovery can open another incident; your PagerDuty service controls escalation and responder notifications.

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. Confirm the labeled test incident appears in PagerDuty. Statusfield also sends a follow-up resolve event; check that it resolves, and close it manually if the follow-up did not arrive.
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)

Statusfield sends a resolve event when the monitored service returns to Operational. Keep the destination and its alert rule active so the recovery event can be delivered.

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: shared by related updates and their recovery, with separate keys for regional endpoint checks

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

  • Check whether the monitor has returned to Operational and whether the destination and its notification rule are still active. If Statusfield sent a resolve event, check its delivery result and the matching PagerDuty incident.

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