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日 清晨6:05 · 目錄修訂版 5bc079fe355af2214bc0
正在顯示應用程式內建的快照(尚未設定內容來源)。來源處可能已有更新的內容。