Follow one checkout outage from investigation to service recovery and prevention. The guides below explain what to enter, what to inspect, and how to interpret the result. Screenshots show the application itself with reviewed demo values.
These are actual PulseServe screens rendered with fictional documentation fixtures. INC0000001 uses the seeded checkout outage scenario; the related problem, change plans, users, and dates are illustrative. This resolved example shows a completed investigation. Available tabs and actions depend on your role, permissions, configuration, and ticket state.
The example and its three records
- INC0000001 records the service interruption: checkout-api starts returning HTTP 500 errors after v2.4.1 is deployed. Service recovery is recorded after 95 minutes.
- CHG0000001 records the deployment, its risk, review, schedule, implementation, test, and backout plans. It gives the investigation a concrete change candidate.
- PRB0000001 tracks prevention: remove the N+1 query regression permanently and validate the fix. The incident can be resolved while this problem remains a known error, with a separate draft RFC (CHG0000002) for the permanent correction.
Where to find each area
- Left navigation → My Work → Incident-Mgmt opens the incident queue.
- Left navigation → Change Mgmt → Change-Mgmt or Problem-Mgmt opens changes or problems. Select a record to see its detail panel.
- Top bar → Admin → Admin Console opens user and access administration.
- The settings gear opens Settings. Expand a section to inspect its controls.
- Top bar → Insights → Reports or Report Builder opens fixed exports or custom analysis.