...

It is also worth to mention the way Apache CXF attaches the description to observations (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 Micrometer Observation and JAX-WS support

TBD

Accessing Micrometer Observation APIs

TBD

Using non-JAX-RS clients

TBD