Page History

...

By default, ObservationClientProvider will use configured propagators to pass the currently active observation through HTTP headers on each service invocation. If there is no active observations, the new observation will be created and passed through HTTP headers on per-invocation basis. Essentially, for JAX-RS applications just registering ObservationClientProvider on the client and ObservationProvider on the server is enough to have tracing context to be properly passed everywhere. The only configuration part which is necessary are span reporter(s) / exporter(s) and sampler(s) which are, not surprisingly, specific to distributing tracing bridge you have chosen.

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