liveBook · Manning

Observability

As explained in Grokking Software Architecture

Observability is the practice of making a distributed system's internal state inferable from externally emitted telemetry.

Observability makes a running system’s internal condition inferable from its outputs, such as logs, metrics, and traces. It matters when software is running in the wild and you need to see what is happening inside. section 2.4 section 7.6.5

In distributed systems, telemetry is your view from the ground: correlation IDs can connect one service’s crash to an error in another. section 7.6.5

Follow the error

A correlation ID links an OrderService crash to a ShippingService error, helping reveal the story across services. section 7.6.5

How Grokking Software Architecture covers it

How deep it goes
Defines observability through logs, metrics, and traces, then ties telemetry and correlation IDs to service failures without detailing instrumentation.
Examples
Uses Apollo 13 telemetry and a correlated OrderService crash and ShippingService error as illustrations.
What you can do after
Understand how telemetry and correlation IDs help infer system behavior and connect distributed-service errors.
How it connects
Links observability with logs, metrics, traces, correlation IDs, and distributed systems.

Also explained in

Compare how 25 books explain observability →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.