Telemetry

As explained in Google Anthos in Action

Telemetry is automatically collected information about system or service behavior, including metrics, logs, and traces.

Telemetry is automatically collected information about service behavior, including metrics, logs, and traces. In a service mesh, proxies observe inbound and outbound traffic and forward this information to centralized monitoring systems without application changes. section 4.2 section 4.5.2

Telemetry supports several operational activities:

• Collect metrics and logs from Envoy proxies and TCP sessions, with customizable Istio metrics. section 4.3.4
• Trace distributed transactions, investigate latency, analyze service dependencies, and perform root-cause analysis. section 4.3.4
• Visualize service topology, health, performance, latency, errors, and traffic across microservices. section 4.5.2 section 5.1.5
• Support service-level indicators, service-level objectives, scaling decisions, optimization, and postmortems. section 4.5.2 section 5.1.5

Mesh telemetry path

A sidecar proxy attached to each Pod intercepts microservice traffic, collects metrics and logs, and sends them to Anthos Service Mesh, Google Cloud Monitoring, or Google Cloud Logging. Kiali can build a service graph from the resulting data, while Prometheus and Grafana support querying, visualization, and alerting. section 4.2 section 4.3.4 section 4.5.2

Figure 4.1 Sidecar proxy architecture

Use the sidecar architecture diagram to follow how a proxy shares a microservice’s lifecycle while running as a separate process. section 4.2

How Google Anthos in Action covers it

How deep it goes

Explains collection paths, observability tools, and operational uses, but stops short of detailed telemetry schemas or instrumentation code.

Examples

Uses Envoy sidecars, Kiali service graphs, Prometheus time series, Grafana dashboards, and Google Cloud Monitoring and Logging.

What it assumes

Assumes microservices and service-mesh components, while treating application-level instrumentation as unnecessary for proxy-collected telemetry.

What you can do after

Diagnose/debug with it by tracing latency, inspecting traffic and dependencies, reviewing service health, and analyzing historical failures.

How it connects

Connects telemetry with service meshes, sidecar proxies, Envoy, Istio, distributed tracing, Prometheus, Grafana, and service-level indicators.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Effective Platform EngineeringTelemetry data consists of automatically emitted records such as metrics, logs, and traces that describe software-system behavior, performance, and state.
• 

  liveBookmanning.com
  Secure APIsData and signals emitted by software about its execution, health, and behavior.
• 

  liveBookmanning.com
  Cloud Observability in ActionTelemetry is the process of collecting signals from sources, processing them, and ingesting them into destinations for consumption.
• 

  liveBookmanning.com
  Logs and TelemetryTelemetry data is machine-generated information about software or infrastructure behavior, including logs, metrics, and traces.
• 

  liveBookmanning.com
  Build an AI Agent (From Scratch)Operational data and signals generated by a running system and transmitted for monitoring and analysis.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesTelemetry is automatically generated data about software and system behavior, including metrics, logs, and traces.
• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureAn event containing measured operational data emitted by a device or system.

Compare how 8 books explain telemetry →

Related concepts

• observabilityused by · Observability is the ability to infer a system’s internal state and behavior from its externally available outputs, such as logs, metrics, and traces.
• trajectoryhas part · A trajectory is an ordered sequence of states, actions, events, or operations that records or describes progression through successive steps or over time.
• instrumentationproduced by · Instrumentation is the addition or activation of mechanisms in software or systems to observe, measure, or record their behavior during execution.
• monitoringincludes · Monitoring is the ongoing observation and measurement of a system’s behavior, state, or operational signals to assess its condition and detect changes or problems.
• OpenTelemetryproduced by · OpenTelemetry is an open, vendor-neutral observability standard and framework for instrumenting software and generating, collecting, and exporting telemetry such as traces, metrics, and logs.
• metrichas part · A metric is a quantitative measure used to characterize or assess a property, condition, behavior, performance, or outcome.

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.