[
https://issues.apache.org/jira/browse/CAMEL-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070584#comment-18070584
]
Bjorn Beskow edited comment on CAMEL-23283 at 4/6/26 2:23 PM:
--------------------------------------------------------------
Pull request [https://github.com/apache/camel/pull/22410] for the new component
{{camel-micrometer-observability}} created with a test that highlights the
problem, and corrects the root cause.
was (Author: beskow):
Pull request [https://github.com/apache/camel/pull/22410] for the new component
```camel-micrometer-observability``` created with a test that highlights the
problem, and corrects the root cause.
> OpenTelemetry/Micrometer traces are not exported for JMS-initiated routes
> -------------------------------------------------------------------------
>
> Key: CAMEL-23283
> URL: https://issues.apache.org/jira/browse/CAMEL-23283
> Project: Camel
> Issue Type: Bug
> Components: camel-tracing
> Affects Versions: 4.15.0, 4.16.0, 4.17.0, 4.18.0, 4.18.1
> Reporter: Bjorn Beskow
> Priority: Major
>
> When using camel-observability or camel-micrometer-observability, traces and
> spans are correctly created and exported for routes triggered by other,
> tracing-aware framework components (e.g. http). If a route is triggered by a
> jms message, no trace or span is exported however.
> This seems to be caused by missing scope management:
> MicrometerObservabilitySpanAdapter::activate() only calls span.start() but
> doesn't put the
> span into the tracer's thread-local scope. This means tracer.currentSpan()
> returns null during route execution, hence the span is invisible to
> downstream instrumentation that relies on tracer.currentSpan() to find a
> parent span.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
