Back to list
Lv.3

Observability

Observability

The property of a system that lets you infer and understand its internal state from the data it outputs.

In Simple Terms

Observability refers to the quality of a system that makes it easy to understand and investigate what's happening inside, based on the data it produces externally. For example, it helps you trace the cause when an app suddenly slows down, or catch hidden issues before they turn into errors — it's useful in all kinds of situations. It's an essential concept for keeping complex systems running reliably.

Behind the Name

The word "Observability" comes from "Observable" — something that can be watched or measured from the outside. It describes how easily you can understand what's happening inside a system just by looking at its outputs. In software development, it's seen as a step beyond simple monitoring.

Take a Closer Look!

Observability is the property of a system that lets you infer and understand its internal state from the data it outputs externally.
The idea is to ensure both the quantity and quality of output data — such as logs, metrics, and traces — so that even unexpected issues can be traced back to their root cause afterward.

Traditional system monitoring focused mainly on detecting predefined failure patterns.
However, in complex environments where many small systems work together, unexpected problems become far more likely.
So instead of simply knowing that "the system went down," teams need a way to thoroughly investigate "why it went down" and "what went wrong" — after the fact.

Concretely, this involves collecting and analyzing three types of data that systems produce: logs (records of operations), metrics (numerical measurements), and traces (the paths requests travel through the system).
Keeping these well-organized makes it much easier for developers to investigate the root cause of issues and apply fixes quickly.
The result is more stable, reliable service for users.