Worlds / Eng and it ops / PagerDuty
PagerDuty world
A local PagerDuty with services, incidents, escalation policies, schedules and on-call users. Test the incident agent that acknowledges, reassigns, merges and resolves incidents.
IncidentsEscalation PoliciesSchedulesServicesMerges
| Incident | Service | Assigned to | Status |
|---|---|---|---|
| #3012 High 5xx on checkout | checkout-api | Ana (primary) | TriggeredAcknowledged |
| #3013 High 5xx on checkout | checkout-api | Ana (primary) | TriggeredResolved · merged |
| #3009 Disk 92% db-2 | postgres | Leo (primary) | AcknowledgedResolved |
| #3001 Cert expiry warning | edge | Sam (secondary) | Triggered |
| #2998 Queue lag | workers | Ana (primary) | Resolved |
fig. 1 · illustrative replica · the agent's changes land as you scroll
What's in this world
What you get when you open PagerDuty. Seeded, local, yours to break.
Seeded records
- services
- 12 services with integrations and urgency rules
- incidents
- 40 triggered, acknowledged and resolved
- escalation policies
- 3 levels with timeouts
- schedules
- Primary and secondary on-call rotations
- users
- 25 responders with contact methods
Agent jobs you can test
- Acknowledge and route new incidents to the right responder
- Merge duplicate incidents into one
- Resolve incidents after the alert clears
What your agent can get wrong here
The reply sounds right. The record is what counts.
ActionWhat the world recordsCommon mistake
Merge incidents
merged incident and its alertsMerges incidents from two different servicesResolve an incident
incident status and the source alertResolves #3009 while the disk alert is still firingReassign
assignments and escalation levelPages the whole escalation policy instead of one responderAdd a note
incident notesPosts the note on the wrong incidentExample test
Describe the job. Review the checks before anything runs.
Handle the open checkout incidents. Acknowledge #3012, merge the duplicate #3013 into it, and leave the database incident to its owner.
- 01#3012 acknowledged
- 02#3013 merged into #3012
- 03#3009 still acknowledged
- 04No one outside primary on-call paged
- 05Escalation policies unchanged
fig. 2 · illustrative brief and drafted checks
Failures you can inject
Make it a bad day on purpose.
effect
The REST API returns 429fires before the handler · state untouched · same result every runEvidence
StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations
