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 2013/03/28 07:07:16 UTC

[jira] [Commented] (CAMEL-5698) Allow to set a custom LogFormatter in the Log component

    [ https://issues.apache.org/jira/browse/CAMEL-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616090#comment-13616090 ] 

Claus Ibsen commented on CAMEL-5698:
------------------------------------

btw if you want different formatter for an endpoint, you can just refer to another using
{code}
.to("log:foo?exchangeFormatter=#myFormatter")
.to("log:bar?exchangeFormatter=#myOtherFormatter")
{code}

You get this out of the box by having java bean getter/setters on the endpoint class.

                
> Allow to set a custom LogFormatter in the Log component
> -------------------------------------------------------
>
>                 Key: CAMEL-5698
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5698
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.9.3, 2.10.1
>            Reporter: Raul Kripalani
>            Assignee: Raul Kripalani
>            Priority: Minor
>             Fix For: 2.11.0
>
>
> The LogFormatter should be configurable. Then one can:
> - filter the headers and properties that are printed (try logging with showHeaders=true after an InOut CXF invocation and you get information overdose)
> - adjust the log message to whatever they deem most readable
> - tailor log messages for processing by log mining systems, e.g. Splunk
> - print specific body types differently
> - etc.

--
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