liveBook · Manning

OpenTelemetry

As explained in Troubleshooting Java, Second Edition

OpenTelemetry is an open-source observability framework and standard for collecting, generating, and exporting telemetry such as traces, metrics, and logs.

OpenTelemetry is the observability layer that generates telemetry from running Java services, especially distributed traces composed of trace IDs and spans. It supports manual instrumentation in application code and automatic instrumentation through the OpenTelemetry Java agent, which attaches at startup without code changes. section 12.1.2

A practical tracing setup connects:

Figure 12.3 OpenTelemetry collects relevant data from the running service. Jaeger and Zipkin are tools that aggregate and display nicely this data to help you easily troubleshoot the system.

Use the architecture diagram to follow telemetry from a running service through OpenTelemetry to a tracing backend. section 12.1.2

How Troubleshooting Java, Second Edition covers it

How deep it goes
Explains manual and automatic instrumentation, export, and backend roles, but stops short of detailed configuration or code examples.
Examples
Uses a missing-order investigation and a service-to-backend architecture diagram as concrete tracing examples.
What it assumes
Assumes Java services and a deployed runtime environment, while distinguishing developer instrumentation from platform-managed tracing infrastructure.
What you can do after
Diagnose distributed-service failures by generating spans and exploring exported traces in Jaeger or Zipkin.
How it connects
Connects distributed tracing with trace IDs, spans, Jaeger, Zipkin, OTLP, gRPC, and observability infrastructure.

Also explained in

Compare how 7 books explain OpenTelemetry →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Troubleshooting Java, Second Edition. The section links point to the parts of the book it draws on.