liveBook · Manning

OpenTelemetry extension

As explained in Quarkus in Action

The OpenTelemetry extension is a Quarkus extension that integrates application instrumentation with OpenTelemetry telemetry generation and export.

The OpenTelemetry extension adds tracing to Quarkus services without changes to application code. Adding it to the Users, Reservation, and Inventory services enables automatic collection of tracing data across service calls. section 10.4.2

Exporting traces to Jaeger

Start Jaeger with Docker Compose, then run the three applications in Dev mode. Jaeger receives OpenTelemetry data on port 4317 and exposes its tracing UI on port 16686; the extension’s default export target requires no application configuration. section 10.4.2

How Quarkus in Action covers it

How deep it goes
Demonstrates installation, runtime collection, Jaeger export, and UI inspection, but does not detail instrumentation internals.
Examples
Traces Users, Reservation, and Inventory services, then inspects service lists, traces, tags, and span graphs in Jaeger.
What it assumes
Assumes existing Quarkus services and a container runtime, while introducing tracing setup through the extension and Jaeger.
What you can do after
Operate distributed tracing by installing the extension, starting Jaeger, generating requests, and inspecting resulting spans.
How it connects
Connects Quarkus extensions with OpenTelemetry, Jaeger, OTLP, Docker Compose, and distributed tracing.
Cover of Quarkus in Action
liveBookmanning.com
Read Quarkus in Action on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.