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
앱에 내장된 스냅샷을 표시하고 있습니다(콘텐츠 소스가 설정되지 않았습니다). 소스에는 더 새로운 콘텐츠가 있을 수 있습니다.