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:11:04 UTC

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

     [ https://issues.apache.org/jira/browse/CAMEL-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-11360:
--------------------------------
    Attachment: before.png
                after.png

By disabling the old tracer we no longer have many TracedRouteNodes created during routing.

> 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
>
>         Attachments: after.png, before.png
>
>
> 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)