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 "Gary Gregory (JIRA)" <ji...@apache.org> on 2015/06/10 05:28:01 UTC
[jira] [Commented] (LOG4J2-1023) New RewritePolicy for changing
level of a log event
[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579973#comment-14579973 ]
Gary Gregory commented on LOG4J2-1023:
--------------------------------------
The name of the @PluginElement is the same as the class name: LoggerNameLevelRewritePolicy.
Please verify and close.
> New RewritePolicy for changing level of a log event
> ---------------------------------------------------
>
> Key: LOG4J2-1023
> URL: https://issues.apache.org/jira/browse/LOG4J2-1023
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.3
> Reporter: Mikael Ståldal
> Labels: configuration
> Fix For: 2.4
>
>
> It would be useful to have a RewritePolicy for changing the level of a log event.
> Some 3rd party libraries log stuff on wrong level, and I would like to be able to translate it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org