[
https://issues.apache.org/jira/browse/CAMEL-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pasquale Congiusti closed CAMEL-17595.
--------------------------------------
Resolution: Fixed
With the new [camel-telemetry
component|https://camel.apache.org/components/next/others/telemetry.html], this
feature isn't required. The default behavior is to start a new trace for any
new Exchange, so, in case of aggregation, you will see the "aggregate" eip span
attached to each trace. This aggregate span will be eventually closed when the
trigger is executed.
As a general rule of thumb, for any tracing manipulation, within the new
component you can fully play with exchange headers. However, the settings of
the headers will depend on the specific tracing technology adopted (ie, otel vs
micrometer observability).
> camel tracing - reset trace in route
> ------------------------------------
>
> Key: CAMEL-17595
> URL: https://issues.apache.org/jira/browse/CAMEL-17595
> Project: Camel
> Issue Type: New Feature
> Components: camel-tracing
> Reporter: Sijmen Huizenga
> Priority: Minor
> Fix For: 4.x
>
>
> Add the ability to start a new trace during the exeuction of a route.
> For example, we use an {{aggregate}} with {{completionInterval}} to group
> messages. All messages from the aggregate share the same traceID. This
> results in a single trace spanning all messages over many weeks. We would
> like each message after the aggregate to receive a new trace to improve
> visibility. Having the ability to manually close & start the trace would be
> ideal.
> It would be amazing if it would be possible to call _.reset()_ method from
> the {_}ActiveSpanManager{_}:
> {code:java}
> .process(e -> ActiveSpanManager.reset(e)) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
