[
https://issues.apache.org/jira/browse/CAMEL-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6148.
--------------------------------
Resolution: Fixed
We have a basic implementation now. That is good for now. Can always improve if
needed. For example with more options on the Karaf command, such as filtering
messages etc.
> BacklogTracer - Allow to capture message tracers and store in backlog for
> retrieval on demand (pull based)
> ----------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6148
> URL: https://issues.apache.org/jira/browse/CAMEL-6148
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.11.0
>
>
> A new type of message tracer in Camel that stores the traced messages in an
> internal backlog queue, which can be access on demand by management API.
> This allows us to build a karaf command to show messages traces, and allow
> end users to integrate this easier with their JMX tooling etc.
> The name BacklogTracer was chosen as MessageTracer would be ambiguous with
> the existing Tracer.
> The existing Tracer is too fine grained and has some awkward issues as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
