Skip to Content
97 Things Every SRE Should Know
book

97 Things Every SRE Should Know

by Emil Stolarsky, Jaime Woo
November 2020
Beginner to intermediate
250 pages
7h 41m
English
O'Reilly Media, Inc.
Content preview from 97 Things Every SRE Should Know

Chapter 30. Methodological Debugging

Avishai Ish-Shalom and Nati Cohen

SREs often debug in production—under stress and flooded with information. Debugging can seem like a mysterious, innate trait, but luckily this is untrue; rather, you can follow a structured methodological process to pinpoint the problem, avoiding mistakes and cognitive biases.

  1. Triage: In dealing with an incident, we first must make some meta-decisions quickly: What’s the business impact? Are we handling this incident now or can it be deferred? Do we have time to debug it or should we employ an emergency failover procedure? Many of the answers are unknown before you begin debugging. Triage is a short phase to answer these questions quickly, before launching into a possibly long debugging process. However, you can go back to it at any point: think of triage as a fail-fast step to return to any time you have more data.

  2. Operational definition: To solve an issue we decide is worth pursuing, we need to define it precisely and measurably (“it’s slow” doesn’t cut it). An operational definition has two main parts: a method of measurement (i.e., From where? With which tools? When? In which environment?) and an expected result of that measurement (e.g., “p99 of transaction X is consistently over ...

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 Engineering Manager Should Know

97 Things Every Engineering Manager Should Know

Camille Fournier
97 Things Every Cloud Engineer Should Know

97 Things Every Cloud Engineer Should Know

Emily Freeman, Nathen Harvey

Publisher Resources

ISBN: 9781492081487Errata Page