[
https://issues.apache.org/jira/browse/CAMEL-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029982#comment-18029982
]
Pasquale Congiusti commented on CAMEL-22478:
--------------------------------------------
This one is only about the possibility to expose the information created by the
telemetry choice (whichever it is). I think could be useful for those users
that want to visually see by looking at the log (via MDC tracing). Nothing else
will change. The context propagation will continue as it normally does as that
one is a feature of the telemetry component. I have no strong opinion where to
put that, if in headers or properties. I am curious to know what would be the
pro and cons in each case, do you have any in particular?
About the difference between this and breadcrumid, I think that it is about who
is generating such UID. In this feature case it's generated by the telemetry
engine, not by Camel (as I understand it happens for breadcrumb).
> [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)
