CODING · Dev & Data
Production Error Log Root-Cause Triage & Blameless Incident Postmortem Generator
Drowning in cascading stack traces during an outage? Use AI to separate root-cause exceptions from downstream timeout noise, then turn chat war-room timelines into a Google SRE blameless postmortem.
CORE TOOLS
DeepSeek R1 / Claude 3.7, ELK / Loki Log Snippets
BEST FOR
Backend engineers, SREs, DevOps teams, Engineering Managers
REQUIREMENTS
Sanitized stack traces and incident notes; DeepSeek R1 or Claude
✦ WHY THIS WORKFLOW
Bad postmortems blame "human carelessness," guaranteeing the same outage happens again to someone else. A structured 5-Whys SRE postmortem turns every incident into permanent architectural immunity.
✦
Interactive Workflow Animation Preview
Step-by-Step Action Checklist
0 / 4 Completed
READY-TO-USE PROMPT TEMPLATE
Act as a Principal Google SRE. Below are sanitized error logs and war-room timestamp notes from a production incident: [Paste logs & incident chat notes] Deliver: 1) [Causal Chain Analysis]: Separate downstream cascading symptoms (timeouts, thread pool exhaustion) from the true primary trigger; 2) [Executive Impact Summary]: Duration, blast radius, TTD (Time to Detect) and TTR (Time to Mitigate); 3) [Minute-by-Minute Incident Timeline Table]; 4) [Blameless 5-Whys Analysis]: Focus strictly on missing systemic guardrails rather than individual human error; 5) [Prioritized Action Items]: Grouped into Immediate Hotfix, Short-Term Alerting/Testing, and Long-Term Architectural Resilience.