Verification & blameless review

Close the incident with a follow-up

Lesson 19 of 20 · 12 min · Module 6: Recover a complete service

Recovery restores service; follow-up work reduces the chance or impact of recurrence.

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…

  • Use evidence to declare recovery
  • Describe a contributing system condition

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.

01Use evidence to declare recovery

The service should be healthy and its critical behavior checked before the incident is resolved. A quiet alert alone can be misleading.

02Describe a contributing system condition

A blameless review asks how the process allowed the failure and what information was available. It avoids substituting blame for a useful explanation.

03Choose an actionable improvement

A specific smoke-gate improvement is easier to own and verify than an instruction to be more careful. Track it beyond the incident document.

Your turn

Open incident "Bad release" owned by oncall. Deploy notes:2.0, roll back notes:1.0, smoke, and resolve. Add review.cause "Missing smoke gate" and review.followup "Add preproduction smoke check".

What the checks look for

  • Resolves the owned incident after recovery
  • Records a concrete system improvement
Try it in the editor →

Take this with you

Recover the service and improve the conditions that shaped the failure.

Go a little further

Add an owner and acceptance criterion to the proposed follow-up action.

Learn Infrastructure & Operations for free

20 short lessons with real code and instant checks.

See the whole course →