Currently we have support for both OpenTracing and OpenTelemetry. Because of OpenTracing deprecation, we should not take it into account during the Quarkus migration but just enable OpenTelemetry.

• Investigating using OpenTelemetry with Quarkus .
• How to deal with our config/application.properties based configuration using bridge.tracing with the Quarkus properties?
• Removing the usage of RoutingContext for all the endpoints which need it just for the tracing (i.e. using RoutingContext to inject/get tracing headers from/to HTTP request/response).