[
https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135276#comment-13135276
]
Ralph Goers commented on LOG4J2-54:
-----------------------------------
For all intents and purposes, yes it is immutable. An Appender that wraps other
Appenders can create a new LogEvent from the one passed to it and give the new
LogEvent to the Appenders it wraps. The RewritePolicy interface takes a
LogEvent as a parameter and returns one as the result.
> Support existing ability to modify any of an event's fields
> -----------------------------------------------------------
>
> Key: LOG4J2-54
> URL: https://issues.apache.org/jira/browse/LOG4J2-54
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: scott deboy
>
> RewriteAppender and RewritePolicy in log4j 1.2 give appender writers the
> ability to change events before they are sent to appenders. Two examples:
> adding properties to all events using PropertyRewritePolicy, and X-ing out
> passwords and sensitive text, logger names truncating stack traces because of
> sensitive class information.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
