PagerDuty integration
Sync PagerDuty users, teams, and service data to automatically correlate incidents with tickets and accelerate incident response.
What it connects
- User accounts and on-call rotations across all teams and escalation policies.
- Organizational team structure and service ownership relationships.
- Technical services monitored for incidents with escalation rules and coverage gaps.
- Schedule and on-call roster data to identify available responders.
What it automates
- Create incidents on services with automatic escalation based on on-call schedules.
- Acknowledge or resolve incidents and automatically update linked tickets.
- Suppress alerts during maintenance windows to prevent false incident creation.
- Add incident notes and create on-call schedule overrides for coverage gaps.
In practice
When a P1 incident fires, automatically create a major-incident ticket and route it to the current on-call responder based on PagerDuty escalation policies.
STLabs pulls on-call rosters in real-time, so runbooks and escalation workflows always route to the right team even during schedule changes.
Automatically suppress alerts during maintenance windows by syncing PagerDuty maintenance schedules to prevent incident spam.
Resolve linked tickets when incidents are resolved in PagerDuty, keeping ticket state in sync with actual incident status.
