jam01 opened a new pull request #4001: URL: https://github.com/apache/camel/pull/4001
This is a considerable refactor and change in how OpenTracing works with Camel. First, to address CAMEL-15260 I added an InterceptStrategy that will: * Create Spans for each processor using ids and component names. This was based on the AWS Xray component * Opens/closes a Scope around each processor. Having opened Scopes within each processor enables two big features: * Allows any instrumentation library from opentracing-contrib to pick up the active Spans and use it to create child ones. This should work with or without java agent instrumentation. * Gives the user direct access to the active Span for any custom functionality Second, it changes the the behavior of the OpenTracingTracer to only create one Server Span. Conceptually there should only be a single Server Span while in-process in a single service. @mcrmfc , this is the approach I was thinking should be implemented. Would this work for your use case ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
