[
https://issues.apache.org/jira/browse/CAMEL-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029870#comment-18029870
]
Raymond commented on CAMEL-22478:
---------------------------------
Some questions on this issue:
1. How does the traceid differs from the breadcrumbid?
2. Is it useful to put it in the headers that users are using, or is it better
to have as exchangeProperties or somewhere as a separate exchange parameter
where it doesn't affect the message.
3. Will this traceid stay within the Camel context, or does it also travel
outside (for example when using ActiveMQ or calling a HTTP endpoint)?
4. Will the traceid also be used outside MDC/Logging, for example for tracing
of messages?
> [camel-telemetry] Introduce traceid/spanid exchange headers
> -----------------------------------------------------------
>
> Key: CAMEL-22478
> URL: https://issues.apache.org/jira/browse/CAMEL-22478
> Project: Camel
> Issue Type: Task
> Reporter: Pasquale Congiusti
> Assignee: Pasquale Congiusti
> Priority: Minor
> Fix For: 4.16.0
>
>
> Now that we have introduced a simpler MDC mechanism we can introduce some
> parameter in all telemetry components and make it easier for the user to
> include traceid/spanid MDC information. In the past we had to deprecate this
> as we had no support for the context propagation. With the new component,
> this is now consistent and we can provide the feature ootb by simply adding
> those Exchange headers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
