[
https://issues.apache.org/jira/browse/CAMEL-23709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086892#comment-18086892
]
Claus Ibsen commented on CAMEL-23709:
-------------------------------------
> That was exactly my point: EndpointSpannable is leaking an external domain
> detail (telemetry) into a core component that should be completely agnostic.
> It's doable, but IMO, it breaks software design decoupling.
Okay yeah we can use a better name - EndpointSending as we send to an endpoint
> camel-opentelemtry2 - Span verbosity for core processors that also emit events
> ------------------------------------------------------------------------------
>
> Key: CAMEL-23709
> URL: https://issues.apache.org/jira/browse/CAMEL-23709
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry
> Reporter: Claus Ibsen
> Priority: Major
>
> For EIPs such as to / wireTap / toD and others that emit events (send an
> outgoing message ) then you get double spans, one as a processor and one as
> the event, and they get into a parent/child relationship - which makes the
> span tree very deep.
> IMHO the processor spans should only be for EIPS that do not emit events such
> as split, aggregate, etc.
> The core span has no value for the to, as the value is the span about sending
> event, to capture where its being sent, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
