liveBook · Manning

Instrumentation

As explained in Google Anthos in Action

Instrumentation is the inclusion of code or integrations that emit measurements and diagnostic signals about software execution.

Instrumentation adds code or integrations that emit measurements and diagnostic signals about software execution. During legacy-application modernization, it supports end-to-end observability across distributed operating environments. section 16.1

Operational implications:

  • Replaces dependence on logging into a dedicated virtual machine for viewing logs or debugging. section 16.1
  • Enables teams to monitor and investigate incidents across large sets of nodes. section 16.1
  • Fits alongside migration from virtual machines to containers and managed environments such as GKE or Anthos. section 16.1

How Google Anthos in Action covers it

How deep it goes
Connects instrumentation to end-to-end observability but does not specify signal types, implementation steps, or configuration.
Examples
Uses VM-to-container migration and monitoring across large node sets as operational contexts.
What you can do after
Diagnose incidents across many nodes without relying on access to a dedicated virtual machine.
How it connects
Links instrumentation with observability, logging, containers, virtual machines, and managed container environments.

Also explained in

Compare how 13 books explain instrumentation →

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.