Skip to main content

​
Overview

The PagerDuty integration enables Steadwing to query incidents, alerts, and response metrics from your PagerDuty account. During root cause analysis, Steadwing pulls incident timelines, escalation patterns, and alert details to correlate on-call response with production incidents.

​
Why Use PagerDuty with Steadwing?

Incident Timeline

Build complete incident timelines with triggers, acknowledgments, and resolutions

Alert Correlation

Connect PagerDuty alerts to monitoring tools like Datadog and Sentry

Response Metrics

Track time to acknowledge and resolve for incident analysis

Escalation Patterns

Understand escalation paths and responder involvement during incidents

​
Setup Instructions

​
Step 1: Create a PagerDuty API Key

  1. Log in to your PagerDuty account
  2. Navigate to Integrations → Developer Tools → API Access Keys
  3. Click Create New API Key
  4. Configure the key:
    • Description: Steadwing Integration
    • Key Type: Read-only API Key (recommended)
  5. Click Create Key
  6. Copy the generated API key
Save your API key immediately! PagerDuty only shows the key once. Store it securely as it provides access to your incident data.

​
Step 2: Connect PagerDuty in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the PagerDuty integration card
  3. Click to expand the collapsible form
  4. Fill in the required fields:
    • API Key: Your PagerDuty API key
  5. Toggle the switch to Enable the integration

​
How PagerDuty Integration Works

​
Data Collection

Steadwing queries PagerDuty for:
  • Incidents - Active and recent incidents by time range and status
  • Alerts - Alerts associated with each incident
  • Log Entries - Complete incident timeline including triggers, escalations, and resolutions
  • Response Metrics - Time to acknowledge, time to resolve
  • Custom Fields - Any custom incident field values you’ve configured

​
Configuration

​
Required Permissions

The PagerDuty API key requires read access to:
  • Incidents - Read incident data and status
  • Alerts - Read alert details and sources
  • Log Entries - Read incident activity logs
Using a read-only API key is recommended. Steadwing only needs to read incident data and never modifies your PagerDuty configuration.

​
FAQs

A read-only API key is recommended. Steadwing only queries incident data and does not need write access to your PagerDuty account.
PagerDuty alerts often contain integration metadata from monitoring tools like Datadog, Sentry, or CloudWatch. Steadwing uses this metadata to correlate incidents across your entire observability stack.
No, Steadwing only has read access. It queries incident data but never acknowledges, resolves, or modifies incidents in PagerDuty.
Steadwing queries incidents around the incident timeframe being analyzed, typically including some buffer time before and after to capture related events.
The integration will not work. Simply create a new API key and update it in Steadwing Settings to reconnect.
Need additional help? Please reach out to us at hello@steadwing.com