liveBook · Manning

Observability

As explained in Google Anthos in Action

Observability is the ability to understand a system's internal state from the outputs it produces, such as metrics, logs, and traces.

Observability makes a distributed system’s internal behavior visible through telemetry generated from its outputs. In Anthos Service Mesh, sidecar proxies intercept service traffic and send telemetry to Anthos Service Mesh, Google Cloud Monitoring, and Google Cloud Logging without application changes. section 4.5.2 section 15.1.6

A practical observability implementation combines:

  • Automatic collection: proxies capture traffic between microservices without requiring developers to instrument application code. section 4.5.2
  • Operational signals: integrated metrics, traffic-flow logs, and service telemetry expose service behavior and dependencies. section 4.5.2 section 15.1.6
  • Service-level views: dashboards provide tables of deployed services and topology maps connecting workloads, Pods, system services, and owners. section 4.5.2
  • Reliability evaluation: SLIs and SLOs connect observed service behavior to customer journeys and SLAs. section 4.5.2 section 15.1.6

Tracing a service dependency

After migrating applications into containers, enable Anthos Service Mesh to map connected services, inspect telemetry, view traffic flows, and identify how a dependency affects an end-to-end customer journey. Use SLOs to judge whether the observed behavior meets the service agreement. section 15.1.6

How Google Anthos in Action covers it

How deep it goes
Explains proxy-based collection, monitoring destinations, dashboards, topology, and SLOs without detailing telemetry schemas or instrumentation internals.
Examples
Uses Anthos Service Mesh dashboards, topology maps, traffic-flow logs, service dependencies, and customer-journey SLOs.
What it assumes
Assumes containerized services, a cluster, service-mesh proxies, and familiarity with metrics, logs, SLIs, SLOs, and SLAs.
What you can do after
Apply it via Anthos Service Mesh to inspect service relationships, review telemetry, and evaluate SLO and SLA impact without changing application code.
How it connects
Connects service mesh, proxies, telemetry, metrics, logging, dashboards, SLIs, SLOs, and SLAs.

Also explained in

Compare how 16 books explain observability →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.