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.
Cette ressource n’est disponible qu’en anglais.
Avant de commencer
- Access to logs and the recent change history.
Étapes
Stabilize first
Stop the bleeding (rollback, feature flag, scale) before investigating. Record timestamps as you go.
À vérifier avant de continuer
- 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.
Utilise: Diagnose a stack traceÀ vérifier avant de continuer
- 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.
À vérifier avant de continuer
- Every action item has a type; owners and due dates are assigned by humans.
Résultat attendu
A resolved incident and a postmortem draft with action items.
Ressources associées
Prompt
Diagnose a stack traceTurns 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.
SélectionnéKitLocalMis à jour avant-hier
debuggingstack-tracetroubleshooting
À propos de ce catalogue
Instantané intégré · publié 15 nov. 2026, 06:05 · Révision du catalogue 5bc079fe355af2214bc0
Affichage de l’instantané intégré à l’application (aucune source de contenu n’est configurée). Du contenu plus récent peut exister à la source.