You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "scott deboy (Created) (JIRA)" <ji...@apache.org> on 2011/10/25 18:52:32 UTC
[jira] [Created] (LOG4J2-54) Support existing ability to modify any
of an event's fields
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Resolved] (LOG4J2-54) Support existing ability to modify
any of an event's fields
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-54.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
Log4j 2 implements RewriteAppender and RewritePolicy.
> 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
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Closed] (LOG4J2-54) Support existing ability to modify any
of an event's fields
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-54.
-----------------------------
Closing since there have been no other comments since this was marked resolved.
> 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
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-54) Support existing ability to modify
any of an event's fields
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135245#comment-13135245 ]
Ralph Goers commented on LOG4J2-54:
-----------------------------------
I see that RewriteAppender was recently added to 1.2. I'll be happy to add the same functionality to 2.0.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-54) Support existing ability to modify
any of an event's fields
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-54) Support existing ability to modify
any of an event's fields
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138087#comment-13138087 ]
Ralph Goers commented on LOG4J2-54:
-----------------------------------
I added the RewriteAppender and RewritePolicy to the experimental Log4j 2.0. I also added a MapRewritePolicy that can modify a MapMessage.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-54) Support existing ability to modify
any of an event's fields
Posted by "scott deboy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135255#comment-13135255 ]
scott deboy commented on LOG4J2-54:
-----------------------------------
Are logging events immutable? Curious how you will add support for the RewriteAppender & policies if that's the case.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org