From 57aa09521c352962e7b0086df8a212e978134ae0 Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Wed, 10 Jan 2024 20:15:42 -0600 Subject: [PATCH] Update postmortem documentation (#16033) We will begin conducting postmortems for critical bugs in addition to outages. 1. How was the bug introduced? 2. What is the gap in our testing process that we didn't find the bug before it was released? 3. How are we going to change our testing (both manual and automated) so that we will catch a similar bug in the future? Why? We want to start evaluating the three questions above for every critical bug so that we can learn and improve our processes. --- handbook/engineering/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index dca1b36a71..a5268a579b 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -260,9 +260,9 @@ Steps to renew the certificate: 11. Adjust calendar event to be between 2-4 weeks before the next expiration. ### Preform an incident postmortem -At Fleet, we take customer incidents very seriously. After working with customers to resolve issues, we will conduct an internal postmortem to determine any documentation or coding changes to prevent similar incidents from happening in the future. Why? We strive to make Fleet the best osquery management platform globally, and we sincerely believe that starts with sharing lessons learned with the community to become stronger together. +At Fleet, we take customer incidents very seriously. After working with customers to resolve issues, we will conduct an internal postmortem to determine any process, documentation, or coding changes to prevent similar incidents from happening in the future. Why? We strive to make Fleet the best osquery management platform globally, and we sincerely believe that starts with sharing lessons learned with the community to become stronger together. -At Fleet, we do postmortem meetings for every production incident, whether it's a customer's environment or on fleetdm.com. +At Fleet, we do postmortem meetings for every service or feature outage and every critical bug, whether it's a customer's environment or on fleetdm.com. - **Postmortem documentation** Before running the postmortem meeting, copy this [Postmortem Template](https://docs.google.com/document/d/1Ajp2LfIclWfr4Bm77lnUggkYNQyfjePiWSnBv1b1nwM/edit?usp=sharing) document and populate it with some initial data to enable a productive conversation.