[jira] [Work started] (CAMEL-21472) Opentelemetry is using the same traceId when exchange is fired from file or timer component

["Pasquale Congiusti (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-21472 started by Pasquale Congiusti.
--------------------------------------------------
> Opentelemetry is using the same traceId when exchange is fired from file or timer component
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-21472
>                 URL: https://issues.apache.org/jira/browse/CAMEL-21472
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-opentelemetry
>    Affects Versions: 4.8.1
>            Reporter: Thomas Gantenbein
>            Assignee: Pasquale Congiusti
>            Priority: Major
>             Fix For: 4.8.2, 4.9.0
>
>
> *Problem*
> When using a consumer like {{timer}} or {{{}file{}}}, the traceId remains the same for all messages. When using a consumer like netty (or, I assume, any other http/tcp-based consumer), every call gets its own traceId as expected.
> See also https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/Same.20OTEL.20trace.20for.20all.20messages.20into.20IBM.20MQ
> *Reproducer*
> [https://github.com/thomas-gantenbein-tga/camel-opentelemetry/tree/main]
> [~pcongiusti], thanks for your answer on Zulip Chat. Let me know if I should further explain or minimize that reproducer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)