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 2017/05/29 14:06:04 UTC

[jira] [Created] (CAMEL-11360) Disable Tracer and use BacklogTracer instead

Claus Ibsen created CAMEL-11360:
-----------------------------------

             Summary: Disable Tracer and use BacklogTracer instead
                 Key: CAMEL-11360
                 URL: https://issues.apache.org/jira/browse/CAMEL-11360
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.20.0


See CAMEL-11359

We have the old tracer logic that is cruft. Its still capturing tracing details during runtime, but that is obsolete with the message history we use instead (eg the stuff that also dumps those route stacktrace errors).

So if users say camelContext.setTracing(true) we can then use BacklogTracer instead to log similar trace events.

This allows us to not capture 2x trace details during routing as message history will be used for both.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)