VIII. Observability
You cannot operate what you cannot see, and in a distributed system a single user request touches dozens of services — so understanding one failure means reconstructing a story spread across the whole fleet. Observability is the property that lets you ask new questions of your system without shipping new code, built from three signals with very different cost profiles: logs, metrics, and traces. This part covers those three pillars, the tools and standards that collect them, and the SLO framework that turns raw telemetry into decisions about reliability.
Topics Covered
Section titled “Topics Covered”- 8.1. The Three Pillars: Logs, Metrics, Traces: The three signals and their cost profiles: structured logging, metric types, the RED/USE methods, and distributed tracing.
- 8.2. Tools and Standards: The observability pipeline: OpenTelemetry, Prometheus and PromQL, Grafana, tracing backends, and eBPF.
- 8.3. SLOs, SLAs, and Error Budgets: Choosing a reliability target: SLIs, SLOs, SLAs, the error-budget model, and reducing operational toil.