You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Pasquale Congiusti (Jira)" <ji...@apache.org> on 2026/05/08 07:12:00 UTC
[jira] [Commented] (CAMEL-23432) [camel-telemetry] Distinguish custom process from inner process
[ https://issues.apache.org/jira/browse/CAMEL-23432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079336#comment-18079336 ]
Pasquale Congiusti commented on CAMEL-23432:
--------------------------------------------
https://github.com/apache/camel/pull/23002
> [camel-telemetry] Distinguish custom process from inner process
> ---------------------------------------------------------------
>
> Key: CAMEL-23432
> URL: https://issues.apache.org/jira/browse/CAMEL-23432
> Project: Camel
> Issue Type: Task
> Reporter: Pasquale Congiusti
> Assignee: Pasquale Congiusti
> Priority: Minor
> Fix For: 4.21.0
>
>
> In telemetry components, the `{{{}traceProcessors{}}}` allows us to trace processors. However this is also including those core processors (log, bean, etc...) that are managed by Camel. It results that whenever we disable this, we also disable those core process from tracing, potentially affecting the normal structure of a trace.
> We must make sure that the flag only affects the custom process and let the regular process be accounted for a trace normally.
> We may include a `disableCoreProcessors` flag to guarantee compatibility with any previous logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)