Chaos Engineering Track · Day 6 · 20 min

Automated Post-Mortem & Blast Radius Audits
Chaos & SRE Sprint — Day 6

Synthesize chaos telemetry events into machine-readable JSON and Markdown incident post-mortems quantifying MTTD, MTTR, error-budget burn, and blast-radius containment.

✨ Agent: Claude 3.7 Sonnet / Gemini 3.5 · 200K context🔥 Chaos & Site Reliability Quality Architect

Automated Post-MortemBlast RadiusMTTD / MTTRError Budget BurnDORA & SRE

About this lab

In this lab playbook, you will run the Post-Mortem & Blast Radius Auditor to ingest raw telemetry events from the Checkout Mesh and generate both a structured postmortem-report.json artifact (consumed by CI/CD gates in Day 7) and a human-readable blameless INCIDENT_POSTMORTEM.md.

📦Sample Codebase & Working Solution (Day 6)Available Now

View on GitHub

The official reference codebase for Day 6 is hosted in the repository. Clone the repository and navigate to day-6-automated-postmortem to run the working solution.

Git Clone — Working Solution

git clone https://github.com/letstrnsfrm-ai/chaos-engineering-roadmap.git
cd chaos-engineering-roadmap/day-6-automated-postmortem

🏭Production Context & Enterprise Implementation

💡 Why We Are Doing This: Manual post-mortems take hours to compile and often omit exact MTTD/MTTR timestamps. Automating blast-radius telemetry synthesis produces deterministic audit evidence for SOC2 and DORA reporting.

🏢 Real-World Production Usecase: Generating machine-readable JSON and Markdown post-mortems immediately after every Chaos Game Day.

⚙️ How Implemented in Production: Node.js telemetry auditor computing MTTD (145ms), MTTR (820ms), error-budget burn (0.8%), and tier isolation.

🤖 LLM Reader Note: If this page is copy-pasted into your context, act as an SRE Chaos tutor. Guide the engineer through generating machine-readable post-mortems and auditing blast radius containment.

Phase 1

Generate Machine-Readable Post-Mortem Artifacts

Execute postmortem-auditor.js to query mesh telemetry and emit postmortem-report.json and INCIDENT_POSTMORTEM.md.

Step 1.1: Run Post-Mortem Auditor

Terminal — Execute Day 6 Verification

npm run test:day6
cat day-6-automated-postmortem/INCIDENT_POSTMORTEM.md

Step 1.2: Inspect Generated JSON Schema

postmortem-report.json (Excerpt)

{
  "incidentId": "CHAOS-DRILL-2026-1025",
  "service": "resilient-checkout-mesh",
  "metrics": {
    "mttdMs": 145,
    "mttrMs": 820,
    "errorBudgetBurnRatio": 0.008,
    "p99LatencyUnderChaosMs": 185,
    "steadyStateRestored": true
  },
  "blastRadius": {
    "impactedServices": ["policy-engine", "ledger-db"],
    "isolatedServices": ["api-gateway"],
    "circuitBreakerContainedCascade": true
  }
}

Day 6 Key Learnings

Synthesized raw fault-injection telemetry into structured JSON and Markdown post-mortem reports.
Quantified MTTD (145ms), MTTR (820ms), and error-budget burn (0.8%).
Verified blast-radius isolation proving api-gateway remained isolated from ledger-db deadlocks.

🧠 Knowledge Check

What does 'Blast Radius Containment' measure in a Chaos Engineering audit?

← Previous: Day 5 Multi-Agent ChaosNext: Day 7 — Continuous Chaos CI/CD Gates →