Skip to main content
PreparationZone Logo
PrepZone

On-Call, Runbooks, and Postmortems

Incident lifecycle, blameless postmortems, runbook templates, and on-call best practices.

Pass checkpoint below

Why this matters

  • This topic directly affects how reliably BookStore reaches production — runbooks and blameless postmortems guide bookstore on-call from alert to stable service..
  • Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
  • Later modules assume you can explain both the why and the concrete file or command involved.
  • Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
LogsStructured JSON, Loki/ELK
MetricsCounters, gauges, Prometheus
TracesSpans, OpenTelemetry

All three correlate via trace ID and service labels

Logs answer what happened. Metrics answer how much. Traces answer where time was spent.

Incident lifecycle

Detect, mitigate, learn: BookStore engineers treat this as part of the standard path from laptop to incident response runbooks readiness. Document decisions in the team runbook so on-call knows which knobs exist.

Key ideas

  • Incident lifecycle — primary idea for incident-response-runbooks
  • BookStore context — catalog API, checkout, and inventory services share the same pattern
  • Automation — prefer pipeline jobs over manual SSH steps
  • Verification — staging must prove the change before prod traffic

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Blameless postmortem
  • Production checklist

Test yourself

Answer these before moving on — recall is what makes it stick.