Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-11360

Optimise - Disable Tracer and use BacklogTracer instead

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.20.0
    • camel-core
    • None
    • Unknown

    Description

      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.

      Attachments

        1. after.png
          103 kB
          Claus Ibsen
        2. before.png
          202 kB
          Claus Ibsen

        Activity

          People

            davsclaus Claus Ibsen
            davsclaus Claus Ibsen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: