[jira] [Closed] (CAMEL-21538) [camel-tracing] Deprecate MDC in favour of implementation specific instrumentation

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

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

Pasquale Congiusti closed CAMEL-21538.
--------------------------------------

> [camel-tracing] Deprecate MDC in favour of implementation specific instrumentation
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-21538
>                 URL: https://issues.apache.org/jira/browse/CAMEL-21538
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 4.9.0
>            Reporter: Pasquale Congiusti
>            Assignee: Pasquale Congiusti
>            Priority: Minor
>             Fix For: 4.10.0
>
>
> In camel-tracing component we're supporting a custom setting of MDC trace_id and span_id. This is requiring a deep coupling between the core and the tracing component and is very error prone as it requires a proper cleaning to avoid that any traces set in the thread previously is not used afterwards. As shown in CAMEL-21472 there are inconsistencies that would suggest to deprecate this feature and favouring the specific tracing implementation (ie, Opentelemetry, Micrometer Observability) instead.
> These frameworks are already providing embedded mechanisms to set and clear the MDC while they manage the related traces/spans.



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