3 ms·
At Google, they do these really awesome post-mortems when there's a major failure. It provides a point of reflection, and are usually well written entertaining
by ndesaulniers 11y ago
At Google, they do these really awesome post-mortems when there's a major failure. It provides a point of reflection, and are usually well written entertaining reads. Didn't know they made (some?) public.
They're a good learning exercise writing one, and is more of a learning exercise than a punishment.
- advisedwang 11y agoIt's worth noting that the publicly posted postmortem is not the same as the internal postmortems (which include much more detail, specific action items, timelines etc). The SRE book (https://landing.google.com/sre/book.html https://landing.google.com/sre/book.html) has a whole chapter on our internal postmortems, which is probably a better learning exercise in how to write one. Source: I work on the team that writes these external postmortems.
- jpatokal 11y agoGoogle publishes a public incident report for all service outages (code red) in the Cloud status dashboard. You can see some in the History page: https://status.cloud.google.com/summary https://status.cloud.google.com/summary Sample: https://status.cloud.google.com/incident/appengine/16002 https://status.cloud.google.com/incident/appengine/16002 Note that the length of the report tends to correlate with the severity of the outages and that disruptions (code orange) disruptions do not get reports. Disclaimer: I work in Cloud Support and write some of these.