You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/05/11 19:04:00 UTC

[jira] [Resolved] (CAMEL-17902) camel-opentelemetry - OTEL MDC keys are not matching OTEL keys

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

Claus Ibsen resolved CAMEL-17902.
---------------------------------
    Resolution: Fixed

> camel-opentelemetry - OTEL MDC keys are not matching OTEL keys
> --------------------------------------------------------------
>
>                 Key: CAMEL-17902
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17902
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-opentelemetry
>    Affects Versions: 3.11.6, 3.16.0
>            Reporter: Hugo Veillette
>            Assignee: Claus Ibsen
>            Priority: Minor
>              Labels: mdc
>             Fix For: 3.17.0
>
>
> The native OTEL MDC keys are not the same as the ones used by Camel OTEL component.
> For instance:
> `trace_id` vs `traceId`
> `span_id` vs `spanId`
> This is causing issue to log the MDC values in a consisting way that affects ability to correlate logs together.
> Could we consider aligning with the OTEL spec for MDC keys?
> Reference:
> https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/logger-mdc-instrumentation.md
> [https://camel.apache.org/components/3.16.x/others/opentelemetry.html#_mdc_logging]



--
This message was sent by Atlassian Jira
(v8.20.7#820007)