Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Overview

OpenTelemetry (formed through a merger of the OpenTracing and OpenCensus projects) is a collection of APIs, SDKs, and tools to instrument, generate, collect, and export telemetry data like metrics, logs, and distributed traces. OpenTelemetry is vendor-neutral open-source observability framework and as an industry-standard, it is natively supported by a number of vendors. From the instrumentation perspective, there is support for quite a few programming languages, including dedicated Java APIs. Starting from 3.5.7 /3.6.2 / 4.0.3 releases, Apache CXF fully supports integration (through cxf-integration-tracing-opentelemetry module) with OpenTelemetry distributed tracing capabilities.

...

It is also worth to mention the way Apache CXF attaches the description to spans. With regards to the client integration, the description becomes a full URL being invoked prefixed by HTTP method, for example: GET http://localhost:8282/books. On the server side integration, the description becomes a relative JAX-RS resource path prefixed by HTTP method, f.e.: GET books, POST book/123

Configuring Client

TBD

Configuring Server

TBD

Distributed Tracing In Action: Usage Scenarios

TBD

Example #1: Client and Server with default distributed tracing configured

TBD

Example #2: Client and Server with nested trace

TBD

Example #3: Client and Server trace with annotations

TBD

Example #4: Client and Server with binary annotations (key/value)

TBD

Example #5: Client and Server with parallel trace (involving thread pools)

TBD

Example #6: Client and Server with asynchronous JAX-RS service (server-side)

TBD

Example #7: Client and Server with asynchronous invocation (client-side)

TBD

Distributed Tracing with OpenTelemetry and JAX-WS support

TBD

Distributed Tracing with OpenTelemetry and OSGi

TBD

Spring XML-Configuration

TBD

Using non-JAX-RS clients

TBD