liveBook · Manning

Tiered telemetry approach

As explained in Google Anthos in Action

A tiered telemetry approach is an observability design that combines telemetry collection and analysis across multiple systems or provider layers.

A tiered telemetry approach combines Anthos-native Cloud Monitoring and Cloud Logging with established partner or open-source logging and monitoring systems. It supports hybrid adoption by preserving current operational practices while providing a backup across provider layers. section 5.1.4

The approach is useful when organizations need to balance native integration with operational continuity:

  • Use Cloud Monitoring and Cloud Logging for current Anthos platform and system data; these services are part of the Anthos suite and carry no extra cost. section 5.1.4
  • Continue using validated solutions such as Elastic Stack, Splunk, or Datadog when teams already depend on them or partners manage their uptime. section 5.1.4
  • Balance points of failure among providers and retain an alternative telemetry path during hybrid migration. section 5.1.4

How Google Anthos in Action covers it

How deep it goes
Explains rationale and trade-offs, but stops short of specifying telemetry routing or deployment procedures.
Examples
Uses Anthos clusters, Cloud Monitoring, Cloud Logging, Elastic Stack, Splunk, and Datadog as concrete telemetry systems.
What you can do after
Apply it to hybrid Anthos deployments while retaining familiar tooling and a backup across provider layers.
How it connects
Connects Anthos with Cloud Monitoring, Cloud Logging, hybrid environments, provider redundancy, and vendor lock-in.

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.