Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.steadwing.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What does the PagerDuty integration do?

The PagerDuty integration feeds incident timelines, alerts, escalation patterns, and response metrics into Steadwing’s root cause analysis giving Steadwing the on-call context needed to correlate responder actions with production incidents. During RCA, Steadwing queries your PagerDuty account for relevant incidents, log entries, and custom fields automatically.

​
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

​
Connection Methods

There are two ways to connect PagerDuty to Steadwing. You can use one or both together.
MethodBest For
Marketplace App (OAuth)Auto-triggering RCA when a PagerDuty alert fires
API KeyQuerying PagerDuty as a data source during RCA

​
Method 1: Marketplace App (OAuth)

Install Steadwing directly from the PagerDuty Marketplace. Once installed, Steadwing automatically launches root cause analysis the moment a PagerDuty alert fires no manual intervention needed.

1-Click Installation

Install Steadwing directly from the PagerDuty Marketplace no manual configuration needed.

Auto-Trigger on Alerts

Steadwing automatically kicks off root cause analysis whenever a PagerDuty alert fires.

In-Depth Analysis & Noise Reduction

Get comprehensive analysis of every alert while filtering out noise.

​
Step 1: Install Steadwing from the PagerDuty Marketplace

  1. Go to the PagerDuty Marketplace (PagerDuty → Integrations → App Registration or Marketplace)
  2. Search for Steadwing and click Install
  3. Authorize the connection it will redirect you back to Steadwing
  1. After the redirect, select your Steadwing organization from the dropdown
  2. Click Complete Setup
  3. The app status will show App installed on the PagerDuty integration card
The Marketplace App handles webhook delivery. Steadwing receives PagerDuty alert events automatically without any additional configuration.

​
Method 2: API Key

Connect PagerDuty as a data source, allowing Steadwing to query incident and alert data during root cause analysis.

​
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 Connect via API Key
  4. Fill in the required fields:
    • API Key: Your PagerDuty API key
  5. Click Connect
Using a read-only API key is recommended. Steadwing only needs to read incident data and never modifies your PagerDuty configuration.

​
What data does Steadwing pull from PagerDuty?

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

​
What permissions does the PagerDuty integration need?

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

​
FAQs

No. The Marketplace App auto-triggers RCA when alerts fire. The API Key lets Steadwing query PagerDuty as a data source during analysis. Using both together gives you full coverage — automatic triggers plus deep data access.
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. Steadwing 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 API Token connection will stop working. 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