[
https://issues.apache.org/jira/browse/CAMEL-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031356#comment-18031356
]
Pasquale Congiusti commented on CAMEL-22478:
--------------------------------------------
Thanks for the feedback. We let the user choose. I can add a parameter to make
the user decide if they want those params into either an header or a property.
As for the higher level API method, no, I don't think it is a wise choice. The
design I have in mind is the opposite, I want to remove the non-core concept
from the core. A trace is a telemetry concept and it can evolve in time (as it
already happened). Through a plugin design we make sure to decouple and let the
core have no design concerns around this aspect.
> [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)
