This one perhaps belongs in a security newsletter, but the failure mode is just so fascinating. A CDN bug led to the loss of millions of dollars worth of Bitcoin.
Google posted a report for the Google Calendar outage last week.
Jeli, authors of the Howie post-incident guide has their own “howie”. It’s a great example of a thorough incident report.
Vanessa Huerta Granda — Jeli
Hopefully not too late, here are some tips as we head into the thick of it.
JJ Tang — Rootly
This article is published by my sponsor, Rootly, but their sponsorship did not influence its inclusion in this issue.
Using their own incident retrospective template, Blameless shows us how to write an incident retrospective.
Emily Arnott — Blameless
Meta has their own in-house-built tool for tracking and reporting on SLIs.
A Posten, Dávid Bartók, Filip Klepo, and Vatika Harlalka — Meta
These folks put everyone on-call by default, and also pay them extra automatically for each shift and even covering for coworkers.
Chris Evans — incident.io
Code that was deployed under a feature flag inadvertently affected all traffic, even with the flag disabled.
Steve Lewis — Honeycomb
By creating SLOs for microservices at various levels of the request tree, they ended up with a morass of arbitrary targets that didn’t relate clearly to the user experience.
Ben Sigelman — Lightstep