[
https://issues.apache.org/jira/browse/CAMEL-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901148#comment-17901148
]
Pasquale Congiusti commented on CAMEL-21472:
--------------------------------------------
Hello. I think that part was kind of introduced on purpose: [1] and [2]. We
need to understand a bit more on the root cause and which is the expected
behavior of the component, how we can tune based on the requirement we have and
if there is any bug we need to fix. I will try to work on all those points. I
had a quick look to understand if the MDC behavior is something we can skip by
configuration, but it seems it does not.
[1]
https://camel.apache.org/components/next/others/opentelemetry.html#_mdc_logging
[2]
https://github.com/apache/camel/commit/04916f4e601d1c1cdb9c22cff9ff40e0a1070ffe
> 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
>
> Attachments: image-2024-11-26-09-59-35-555.png
>
>
> *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)
