Know what changed.
Own what happens next.
Service health with a timeline you can follow.
Incident response with a next step you can name.
A service changed.
Now make the impact, the evidence, and the response clear.
From the first signal
to the last update.
Practice the whole loop with three repeatable scenarios. Nothing is live. Every interaction has a visible result.
See the service picture.
Filter health, inspect a component, and read its synthetic check history.
02 / RESPONDLeave a useful timeline.
Acknowledge ownership, record your thinking, and keep recovery explicit.
03 / COMMUNICATEShow what matters outside.
Preview impact and selected updates without exposing internal notes.
The story of
an incident is
in the details.
Keep observed checks separate from your response. A local acknowledgment records ownership; it does not make a failing service healthy.
Enter the incident roomAPI response checks exceed the example limit.
The dashboard depends on the same API path.
Record the next action. Keep the uncertainty visible.
Some services
are degraded.
We are investigating elevated API response times in this synthetic example.
Clear outside.
Detailed inside.
Internal response notes belong in the incident room. Public-preview updates should explain impact and the next known step.
Choose explicitly which local updates appear in the preview. There is no publish button hiding a real external action.
Open the public previewRepeat the scenario.
Improve the response.
Routine afternoon
A normal synthetic check window, with no active incident.
Load scenario 02DEGRADEDAPI slowdown
Elevated API response times are also affecting the web dashboard.
Load scenario 03INTERRUPTEDSign-in interruption
The sign-in component is unavailable and dashboard access is affected.
Load scenarioA useful exercise.
An honest boundary.
Is Beacon checking real services?
No. The monitor data is deterministic synthetic data. No endpoint, account, credential, or external monitoring connection is used.
What does acknowledgment change?
It records a local response event and ownership state. It does not change the simulated service health. Apply recovery explicitly when completing the exercise.
Are updates published anywhere?
No. You can include a local update in the public-page preview, but it remains in this browser. Internal notes are excluded from that preview.
Can I keep the incident record?
Download the current scenario, service states, baseline chronology, and local response updates as a Markdown report.