Telemetry
Telemetry is machine-generated or automatically collected data describing a system’s operation, behavior, state, or performance.
Effective Platform Engineering
Telemetry data consists of automatically emitted records such as metrics, logs, and traces that describe software-system behavior, performance, and state.
- How it is used
- Supports cross-service diagnosis and engineering and business decisions about system health, feature use, and platform value.
- How deep it goes
- Explains collection choices, alerts, tracing, aggregation, and access through operational scenarios; does not specify record schemas or emitter implementations.
- Examples
- Uses Kubernetes CPU activity, a platform-service adoption target, cross-service incidents, and spreadsheets broken by data-structure changes.
- What you can do after
- Diagnose/debug with it by querying shared telemetry across services and defining alerts for known unhealthy states.
Read how Effective Platform Engineering explains telemetry →
Microservices Patterns, Second Edition
Telemetry is operational data generated by a running system, including logs, metrics, and traces.
- How it is used
- Provides production feedback for understanding application behavior, user activity, and deployment outcomes.
- How deep it goes
- Explains instrumentation and infrastructure responsibilities, while deferring detailed observability patterns.
- Examples
- Uses a canary release with error-rate and latency checks, and feature usage as a signal of value.
- What you can do after
- Evaluate deployment health using telemetry and understand how instrumentation and infrastructure support production feedback.
Read how Microservices Patterns, Second Edition explains telemetry →
Secure APIs
Data and signals emitted by software about its execution, health, and behavior.
- How it is used
- Supports API reliability, security detection, incident investigation, and understanding how users interact with services.
- How deep it goes
- Defines logs, traces, metrics, and instrumentation with practical setup, but stops short of detailed telemetry-storage internals.
- Examples
- Uses API requests, errors, database-query logs, OpenTelemetry spans, endpoint metrics, and unusual user request rates.
- What you can do after
- Operate/configure OpenTelemetry instrumentation, correlate API activity, analyze trends, and design safer security telemetry.
Google Anthos in Action
Telemetry is automatically collected information about system or service behavior, including metrics, logs, and traces.
- How it is used
- Provides automatic visibility into microservice traffic for monitoring, troubleshooting, security, scaling, and operational analysis.
- 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 you can do after
- Diagnose/debug with it by tracing latency, inspecting traffic and dependencies, reviewing service health, and analyzing historical failures.
Designing AI Systems
Operational data emitted by a software system to represent its behavior and health, such as logs, metrics, traces, and generation records.
- How it is used
- Answers operational questions about system behavior, latency, cost, and quality through a unified observability service.
- How deep it goes
- Defines telemetry primitives, automatic collection, publishing, and buffering, then connects them to operational dashboards and debugging.
- Examples
- Uses model request counts, latency distributions, costs, guardrail evaluations, and trace-linked log events.
- What you can do after
- Diagnose production issues by correlating trace waterfalls, logs, and metrics to locate bottlenecks and inspect request behavior.
Cloud Observability in Action
Telemetry is the process of collecting signals from sources, processing them, and ingesting them into destinations for consumption.
- How it is used
- Collects and routes system signals so people and applications can consume them for understanding and influencing operations.
- How deep it goes
- Defines the source-agent-destination pipeline and discusses instrumentation, collection, processing, and signal costs without detailing individual signal implementations.
- Examples
- Uses Kubernetes microservices, application code, APIs, databases, metrics, traces, logs, dashboards, alerts, and long-term storage.
- What you can do after
- Operate telemetry by selecting signals, instrumenting owned sources, collecting them through agents, and sending them to central destinations.
Context Engineering
Automatically collected runtime evidence about a software system's operation, including events, measurements, and request-flow data.
- How it is used
- Supports runtime observability and automated feedback in context-aware AI systems.
- How deep it goes
- Defines logs, metrics, and traces, then details enrichment, feedback, adaptive sampling, and an incident investigation.
- Examples
- Uses a discontinued-plan support answer and its model and retrieval spans to illustrate trace investigation.
- What you can do after
- Diagnose context-related failures by inspecting enriched traces and correlating runtime evidence.
Logs and Telemetry
Telemetry data is machine-generated information about software or infrastructure behavior, including logs, metrics, and traces.
- How it is used
- Uses machine-generated logs, metrics, and traces to support monitoring and observability across distributed systems.
- How deep it goes
- Defines telemetry forms and follows collection, transformation, encoding, transmission, and routing, without detailing individual payload schemas.
- Examples
- Illustrates application-generated logs, metrics, and traces flowing through Fluent Bit to compatible collectors or analysis tools.
- What you can do after
- Evaluate how telemetry moves from applications through collectors and exporters using OTLP-compatible transports.
Build an AI Agent (From Scratch)
Operational data and signals generated by a running system and transmitted for monitoring and analysis.
- How it is used
- Supports agent observability, debugging, evaluation, anomaly detection, and operational response.
- How deep it goes
- Defines telemetry, separates metrics, traces, and logs, and explains instrumentation and export without detailing backend implementation.
- Examples
- Uses agent traces, tool calls, latency, token use, costs, errors, retries, prompts, outputs, and runtime records.
- What you can do after
- Diagnose/debug agent behavior, evaluate reliability and cost, detect anomalies, and inspect request execution through telemetry.
Read how Build an AI Agent (From Scratch) explains telemetry →
Platform Engineering on Kubernetes
Telemetry is automatically generated data about software and system behavior, including metrics, logs, and traces.
- How it is used
- Supports diagnosing distributed-application behavior and performance when services fail or users experience poor responses.
- How deep it goes
- Describes metrics, logs, traces, instrumentation, centralized collection, and dashboards without detailing collector configuration.
- Examples
- Uses centralized service telemetry and an approved-versus-rejected proposals dashboard as concrete examples.
- What you can do after
- Operate services with OpenTelemetry instrumentation and Prometheus-Grafana dashboards for behavior and performance visibility.
Read how Platform Engineering on Kubernetes explains telemetry →
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
An event containing measured operational data emitted by a device or system.
- How it is used
- Supports remote monitoring and connected-boat experiences within an IoT growth strategy.
- How deep it goes
- Defines telemetry through sensor readings and frames its throughput demands without detailing event schemas or processing internals.
- Examples
- Uses boat engine speed, temperature, geofence movement, and thousands of connected devices as concrete telemetry contexts.
- What you can do after
- Evaluate whether an architecture can process telemetry at the scale required by thousands of concurrently connected devices.
Also covered in
- Generative AI in Action
- Tech Startup Toolkit
- Quantization and Fast InferenceIn early access (MEAP)
- Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
- Developer Experience on KubernetesIn early access (MEAP)
- Grokking Software ArchitectureIn early access (MEAP)
- Digital Twins in Action
- Building Distributed Applications that Work
- Quarkus in Action
- Microsoft Azure in Action
- gRPC Microservices in Go
- AI Agents for Offensive SecurityIn early access (MEAP)
What to know first
- monitoringMonitoring is the ongoing observation and measurement of a system or process to assess its behavior or condition and detect changes, failures, or other problems.
- trajectoryA trajectory is an ordered record of states, actions, events, or operations showing how an agent or system progresses through an execution or process.
- observabilityObservability is the ability to infer a system’s internal state and behavior from its externally available outputs, such as logs, metrics, and traces.
- metricA metric is a quantitative measure that assigns values to a property or outcome so it can be assessed, compared, or monitored.
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.
- instrumentationproduced by · Instrumentation is the addition or configuration of mechanisms in software or systems to observe, measure, or record execution and behavior.
- trajectoryhas part · A trajectory is an ordered record of states, actions, events, or operations showing how an agent or system progresses through an execution or process.
- monitoringincludes · Monitoring is the ongoing observation and measurement of a system or process to assess its behavior or condition and detect changes, failures, or other 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.
- log entryhas part · A log entry is an individual record of an event or message, often including a timestamp and contextual information such as its source, severity, or outcome.
Questions about telemetry
What is telemetry?
Telemetry is machine-generated or automatically collected data describing a system’s operation, behavior, state, or performance.
Which Manning books explain telemetry?
Effective Platform Engineering, Microservices Patterns, Second Edition, Secure APIs, Google Anthos in Action, Designing AI Systems, Cloud Observability in Action, Context Engineering, Logs and Telemetry and 3 more.
What should I know before learning telemetry?
Manning books that teach telemetry usually introduce monitoring, trajectory, observability and metric first.
What kinds of telemetry are there?
Kinds of telemetry include monitoring.
What are the parts of telemetry?
Telemetry includes trajectory and log entry.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.










