Stack Monitors
Monitor PagerDuty Incidents with Crowswatch
Monitor incident management activity, on-call schedules, and alert routing across your PagerDuty account directly from Crowswatch.
What This Integration Provides
- Incidents: open incident count, severity breakdown, and time-to-acknowledge
- On-call schedules: who is currently on call across your services
- Services: alert volume and incident rate per PagerDuty service
- Escalation policies: current escalation state for active incidents
- Alert routing: inbound alert volume and suppression counts
Requirements
| Requirement | Detail |
|---|---|
| PagerDuty account | Free or above |
| Read-only API key | Account-level General Access key |
| Estimated setup time | ~5 minutes |
Step 1: Generate Credentials
PagerDuty uses REST API keys for authentication. For monitoring purposes, use a read-only account-level key, which restricts the token to GET requests only.
To create a read-only API key:
- Log in to your PagerDuty account as an Admin or Account Owner
- Go to Integrations → Developer Tools → API Access Keys
- Click Create New API Key
- Enter a description (e.g.
crowswatch-monitor) - Check Read-only API Key to restrict the key to read operations only
- Click Create Key
- Copy the key immediately, as it is only shown once
Step 2: Locate Required IDs
PagerDuty does not require additional IDs beyond the API key. Crowswatch uses the key to discover your services, schedules, and teams automatically.
If you want to filter monitoring to specific PagerDuty services, you can find service IDs in the URL when viewing a service: https://yourcompany.pagerduty.com/service-directory/<SERVICE_ID>
Step 3: Add Credentials to Crowswatch
Navigate to: Crowswatch → Add Service → PagerDuty
| Field | Value |
|---|---|
| API Key | The read-only key generated in Step 1 |
Crowswatch will automatically discover your services, schedules, and teams after connecting.
Available Metrics
Incidents
- Total open incidents
- Incidents by severity (Critical, High, Medium, Low)
- Mean time to acknowledge (MTTA)
- Mean time to resolve (MTTR)
- Incident volume over time
Services
- Incident count per service
- Alert volume per service
- Service health status (healthy / warning / critical)
On-Call
- Currently on-call user per schedule
- Upcoming on-call handoffs
- Schedule coverage gaps
Escalation Policies
- Active escalation count
- Escalations currently in progress
Connect
- Enter your read-only API Key in the Crowswatch form
- Click Verify to confirm the credentials are valid
- Select the services and metrics you want to track
- Click Connect
Security
- Always use the Read-only API Key option. Crowswatch only needs read access
- A read-only key cannot acknowledge, resolve, or create incidents
- If you need to revoke access, delete the key in Integrations → Developer Tools → API Access Keys
- Avoid sharing API keys across integrations
Troubleshooting
Authentication error
Confirm the full key was copied. PagerDuty API keys are 20 characters long. Ensure the key is active and has not been deleted from the API Access Keys page.
Services not appearing
Verify the API key has account-level access (not restricted to a specific team or service). Confirm at least one PagerDuty service exists in your account.
On-call data missing
On-call data requires at least one active schedule in your PagerDuty account. Ensure the schedule has on-call layers configured with users assigned.
Incident data not up to date
PagerDuty's API reflects the current state of incidents, and Crowswatch polls this on a regular interval. If you have just resolved an incident, allow one polling cycle for the count to update.