Skip to Content
97 Things Every Cloud Engineer Should Know
book

97 Things Every Cloud Engineer Should Know

by Emily Freeman, Nathen Harvey
December 2020
Beginner
308 pages
9h 5m
English
O'Reilly Media, Inc.
Content preview from 97 Things Every Cloud Engineer Should Know

Chapter 51. Incident Analysis and Chaos Engineering: Complementary Practices

Ryan Frantz

Learning from failure is extremely useful in a world driven by demands for high reliability.1 Our approach to learning, and which failures we should focus on, may not be clear. Two common avenues to learning are incident analysis and chaos engineering.

Incident Analysis

Well-done incident analysis takes time. Constraining ourselves to a few hours or filling out a template to complete an investigation does not result in high-quality analysis. I’ve observed three outcomes associated with incident analyses: pushing paper, technical teaching, and surfacing surprises.

Pushing Paper

Regulatory requirements or fiduciary responsibility may require your organization to produce reports. In these cases, the value of analysis is largely superficial: it’s part of a process to generate a paper trail. It’s a bureaucratic, defensive procedure. Incident analyses are written to be filed, not read.

Technical Teaching

Imagine you operate an ecommerce site whose API fell over as requests stacked up. Your analysis of this incident is an opportunity to update documentation and procedures that can address technical gaps in people’s understanding of the architecture. This is a way of building systems to be robust in the face of past known conditions.

The value of analysis seems ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

AirBnbBlueOriginElectronic ArtsHomeDepotNasdaqRakutenTata Consultancy Services

QuotationMarkO’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
QuotationMarkI wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
QuotationMarkI’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
QuotationMarkI'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Mark W.
Embedded Software Engineer

You might also like

97 Things Every Data Engineer Should Know

97 Things Every Data Engineer Should Know

Tobias Macey
97 Things Every SRE Should Know

97 Things Every SRE Should Know

Emil Stolarsky, Jaime Woo

Publisher Resources

ISBN: 9781492076728Errata Page