Chapter 3. The Origins of Observability in Software
In Chapter 1, we described observability as a property of system dependability and the sense-making capability of complex systems. In Chapter 2, we talked about how code crosses over from development to production, and how to safely test in prod.
This chapter is written by Charity Majors, in her voice and perspective.
It shares her retrospective on how observability entered the software industry, and how it has changed over time. The popular understanding has diverged from the specific, technical meaning it once had. This chapter is about recovering that meaning, and reasserting the principles that matter most.
If you want to get straight to instrumentation and the practical bits, you have Charity’s blessing to skip ahead.
An Introduction from Charity
Hi! My name is Charity, and I am the cofounder and CTO of Honeycomb. I come from the infrastructure side of the house; I have been an operations engineer, site reliability engineer (SRE), and database reliability engineer, working on systems like Linden Lab, Parse, and Facebook, as both engineer and manager.
For 10 years now, I’ve had a front row seat to the industry’s attempts to make sense of our complex, confusing, interdependent web of software, and I’ve contributed some attempts of my own. It’s a bit ironic, because as an engineer I always hated monitoring and dashboards, but I am no stranger to rage-driven development (it’s actually kind of my thing), and I feel really ...
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