1. WHAT IS OBSERVABILITY?
Observability is the extent to which the internal states of a system can be inferred from externally available data. An observable software system provides the ability to understand any issue that arises. Conventionally, the three pillars of observability data are metrics, logs and traces.
2. WHY DOES IT MATTER?
Observability gives you the ability to understand your system’s state.
It allows you to know how well your system is functioning and tells you where the issues are, and what errors are being generated using data emitted by your systems.
Your observability set up should give you the ability to follow your requests through the system, the microservices it interacts with, the state of the infrastructure that these services run on, and the impact of each of these has on the user experience.
3. 3 PILLARS OF OBSERVABILITY
In software, observability refers to telemetry produced by services.
Observability is divided into three major verticals — metrics, logs, and distributed traces — the so-called three pillars of observability.
4. WHAT IS MEANT BY MONITORING?
Monitoring, by textbook definition, is the process of collecting, analyzing, and using information to track a program’s progress toward reaching its objectives and to guide management decisions. Monitoring focuses on watching specific metrics. Logging provides additional data but is typically viewed in isolation of a broader system context.
5. WHAT IS MEANT BY OBSERVABILITY?
Observability is the ability to understand a system’s internal state by analyzing the data it generates, such as logs, metrics, and traces. Observability helps teams analyze what’s happening in context across multicloud environments so you can detect and resolve the underlying causes of issues.