Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
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.