CHAPTER 2Observability
Growth without observability is guesswork. Observability shines a light on what’s working, what’s not, and what to fix next. It’s how you know if your product is truly performing or just surviving.
It is the foundation of growth engineering because it answers the following questions:
- Is our system healthy?
- Are users even seeing our new, shiny feature?
- How are users interacting with our product?
By monitoring observability data, we can refine user experiences, optimize performance, and run better experiments.
The concept of observability comes from control theory, where it was formally defined in the 1960s by Rudolf E. Kálmán, a pioneer in modern control systems.
His definition: “A system is observable if you can determine its internal state solely by examining its outputs over time.”1
In simpler terms, imagine a box you can’t open (Figure 2-1). Can you figure out what’s happening inside just by watching what comes out?
Figure 2-1: A simplified illustration of observability: the system is a box, but by capturing signals (charts, logs, events), the engineer can understand what’s happening inside.
This idea was essential for early autopilot systems, where engineers needed to infer an aircraft’s internal state (like pitch, velocity, or altitude) from sensor data without ever “opening” the plane.
As software became increasingly complex and distributed, ...
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