[
https://issues.apache.org/jira/browse/CAMEL-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122623#comment-13122623
]
Claus Ibsen commented on CAMEL-4500:
------------------------------------
I suggest to use the same format/logic that we already have on
browseMessageAsXml on ManagedBrowsableEndpoint. Then its consistent, instead of
two different formats.
> Add a Tracer that uses JMX Notifications and provides full details of Camel
> Messages
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-4500
> URL: https://issues.apache.org/jira/browse/CAMEL-4500
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.8.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Labels: jmx, trace
> Fix For: 2.9.0
>
>
> We should create a base for Camel Trace toolings so these can trace the full
> message content.
> The trace event should contain:
> - all Exchange Data including properties
> - all Message Data including headers
> There should be a setting to truncate the message body as it can be quite
> long and often in tracing not all details are needed.
> One question is if this tracing should be combined with the current
> Notifications or should be a separate thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
