News for hackers. Stuff that matters.
Re:Feb 27 2023 GCP Outage Incident Report by notimetorelax on Tuesday March 07, 2023 @01:54PM (#35059497)
Look at the ‘Remediation and Prevention’ section for the fixes. Root cause of an incident is always one, but means to prevent it are multiple.
Re:Feb 27 2023 GCP Outage Incident Report by fulafel on Tuesday March 07, 2023 @02:31PM (#35060022)
Right, but is it the right mental model to demand a root cause to be delivered as the outcome to the investigation, when there are lots of things going wrong and process & architecture problems that make the involved failures fatal.
Re:Feb 27 2023 GCP Outage Incident Report by notimetorelax on Tuesday March 07, 2023 @04:23PM (#35061453)
This follows Google’s published post mortem template: https://sre.google/sre-book/example-postmortem

What you’re saying can go into the lessons learned section.

Re:Feb 27 2023 GCP Outage Incident Report by fulafel on Thursday March 09, 2023 @06:22AM (#35080227)
That template is a bit better wrt the cognitive problem in question since the heading is "root causes" (plural). So it's more compatible with the epistemology that there are lots of interacting evens and properties and doesn't frame your thinking around pinpointing a single event in the complex graph of interacting processes leading to a bad system state. (it's more naturally a graph than a tree whcih is implied by the classic RCA model)