Chapter 7. Monitoring, Logging, and Observability: SRE the Google Way
Most of my career, I’ve worked as a consultant and as a trainer. I would teach for a while, and then some client would say, “Hey, we liked what you taught us, and we were wondering if you could come by for a couple of weeks and make sure we don’t screw up.” Or, more commonly, “We wish we would have had your class six months ago, but we didn’t…and…things aren’t really working. Could you come by and help us get things fixed?” In other words, I spent years and years as a hired gun who got called in to make sure systems didn’t break and, when they did, to help get them working again.
When you go to the doctor and say, “I’m sick,” they ask you some questions, check your temperature, blood pressure, and weight, and maybe run some tests. The doctor is collecting data (symptoms), which hopefully will lead them to a way to make it right.
Monitoring, logging, and observability in Google Cloud serve the same purpose: they give you the data you need to know what’s working in Google Cloud and what isn’t, and, when things aren’t working, they help provide the information you need to make things better.
At the heart of Google’s belief system on how you build reliable systems is site reliability engineering (SRE). We talked about some of these concepts back in Chapter 4, but we left out key details that we need to revisit.
The SRE Approach to System Reliability
Imagine you’re building a house. You could focus entirely on ...
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