Incident response & accountability

Record an incident with an owner

Lesson 14 of 20 · 12 min · Module 5: Evidence and tested recovery

A response needs clear impact and ownership before multiple people start changing the system.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • State the observed impact
  • Name a coordinating owner

The idea

This practice runbook is an ordered sequence of the teaching actions named in the task. Each action changes or observes the supplied in-memory scenario.

01State the observed impact

Describe what users experience. A concrete symptom such as failed notes requests is more useful than an unsupported theory about which person or component is at fault.

02Name a coordinating owner

An owner coordinates diagnosis and communication. That does not mean one person performs every technical action.

03Preserve an open investigation

Collect initial evidence and leave the incident open until recovery is verified. A response process should not confuse acknowledging an incident with resolving it.

Your turn

Open an incident with summary "Notes returns errors" and owner oncall. Then collect logs. Do not deploy or resolve the incident yet.

What the checks look for

  • Records impact and ownership
  • Keeps the investigation open with evidence
Try it in the editor →

Take this with you

Make impact, coordination, and evidence visible early.

Go a little further

Write a short status update that distinguishes observations from hypotheses.

Learn Infrastructure & Operations for free

20 short lessons with real code and instant checks.

See the whole course →