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.
使用するもの: Diagnose a stack trace次に進む前に確認
- 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
アプリに同梱されたスナップショットを表示しています(コンテンツソースが設定されていません)。ソース側にはより新しいコンテンツがある可能性があります。