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 2026/04/13 08:34:00 UTC
[jira] [Commented] (CAMEL-23312) Opentelemetry2: SpanLifecycleManager.create() missing SpanKind parameter causing incorrect span types
[ https://issues.apache.org/jira/browse/CAMEL-23312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18073100#comment-18073100 ]
Claus Ibsen commented on CAMEL-23312:
-------------------------------------
Nice analysis and yeah indeed something that really needs to be fixed
> Opentelemetry2: SpanLifecycleManager.create() missing SpanKind parameter causing incorrect span types
> -----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23312
> URL: https://issues.apache.org/jira/browse/CAMEL-23312
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry
> Affects Versions: 4.18.0
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Major
> Fix For: 4.18.2, 4.20.0
>
>
> The SpanLifecycleManager.create() API lacks a SpanKind parameter:
> Span create(String spanName, Span parent, SpanContextPropagationExtractor extractor);
> This causes all camel-opentelemetry2 spans to default to INTERNAL instead of the
> correct CLIENT/SERVER/PRODUCER/CONSUMER types.
> Expected: HTTP client calls → SpanKind.CLIENT, server endpoints → SpanKind.SERVER
> Actual: All spans → SpanKind.INTERNAL
> The legacy camel-opentelemetry works around this by using custom methods like
> startSendingEventSpan() that accept org.apache.camel.tracing.SpanKind.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)