allthingssecurity commented on PR #29296: URL: https://github.com/apache/camel/pull/29296#issuecomment-6680132093
Yes, I think it can, and it is worth doing on its own. The check in `OpenTelemetryTracingStrategy` (lines 94 and 136) only looks at the outermost `target`. Any strategy registered before it that wraps the processor already defeats it today, independent of the sanitizer. camel-telemetry solves the same problem by walking `DelegateProcessor` until it finds `EndpointSending` (`TraceProcessorsInterceptStrategy.isEndpointSending`, lines 164-177). The same small loop would make the correlation-context check robust. camel-opentelemetry is deprecated in favour of camel-opentelemetry2, which has no such type check, so it is a small fix. With the placement in this design the sanitizer no longer wraps the strategies' `target`, so the design does not depend on it. I'll do it as a follow-up JIRA and PR with a test that registers a wrapping strategy before the OpenTelemetry one. _Claude Code on behalf of allthingssecurity_ -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
