Chapter 2. Fundamentals of Observability
A key part of resilience is our ability to know what is going on, so that we can react, we can plan, and we can learn from what is happening now and from what happens later. Without a sense of what our production system is doing, we are relying on our users to tell us when something goes wrong. And without having information about what our system did at a given point in time, we will find it very difficult to understand what went wrong after the fact. This in turn will massively undermine our desire to continually adapt our system to make it more resilient.
In this chapter, I want to highlight the importance of ensuring that your system is observable. A highly observable system will give you the information needed to know whether the system is resilient enough at a given point in time, and it will become a vital part of adapting your system over longer timescales. This chapter will introduce the fundamental concepts of observability, and in later chapters I’ll highlight other ways in which observability can help.
Observability Versus Monitoring
As is often the case, the concept of observability has been around for decades but arrived in the world of software development only fairly recently. The observability of a system is the extent to which you can understand the internal state of the system from external outputs. It typically requires a more holistic understanding of your software—seeing it as a system rather than as a set of disparate ...
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