Work through a production incident and write it up
From the first error trace to a blameless postmortem: stabilize, diagnose with ranked hypotheses, then document what happened and what to change.
此资源仅提供英文版本。
开始之前
- Access to logs and the recent change history.
步骤
Stabilize first
Stop the bleeding (rollback, feature flag, scale) before investigating. Record timestamps as you go.
继续之前请检查
- Customer impact has stopped or is contained.
Diagnose with hypotheses
Feed the stack trace and what changed into the diagnosis prompt, then run the quickest check for each hypothesis.
继续之前请检查
- At least one hypothesis is confirmed or ruled out with evidence.
Write the postmortem draft
Use the timeline you recorded to draft a blameless postmortem, then refine it with the team.
继续之前请检查
- Every action item has a type; owners and due dates are assigned by humans.
预期结果
A resolved incident and a postmortem draft with action items.
相关资源
Turns a stack trace plus a short description of what you were doing into ranked hypotheses, the first checks to run for each, and what extra evidence would settle it.
精选KitLocal更新于 前天
debuggingstack-tracetroubleshooting
关于此目录
内置快照 · 发布于 2026年11月15日 06:05 · 目录修订版 5bc079fe355af2214bc0
正在显示应用内置的快照(未配置内容来源)。来源处可能已有更新的内容。