[
https://issues.apache.org/jira/browse/CAMEL-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616162#comment-13616162
]
Raul Kripalani commented on CAMEL-5698:
---------------------------------------
Hi [~davsclaus],
Yes, I know.
But I don't see the benefit of setting formatters are the endpoint level. The
goal was to provide a hook for users to customise all output from the Log
component in one shot. Users may pursue this for any one of the reasons
outlined in the ticket description.
To write a one-off custom log message, you are better off using the Log EIP,
which was designed specifically for that purpose.
But hey, my views are personal.
Regards,
Raúl.
> 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