[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406006#comment-17406006
]
Ralph Goers commented on LOG4J2-3151:
-------------------------------------
[~vy] - See
[https://github.com/apache/logging-log4j-audit/blob/master/log4j-audit/log4j-audit-api/src/main/java/org/apache/logging/log4j/audit/AuditLogger.java.]
It logs using Level.OFF specifically because those events cannot be filtered
by log level. So we cannot change that behavior.
[~breun] - Yes, you should prevent them from entering OFF or ALL.
> Messages get logged at level OFF
> --------------------------------
>
> Key: LOG4J2-3151
> URL: https://issues.apache.org/jira/browse/LOG4J2-3151
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.14.1
> Reporter: Nils Breunese
> Priority: Major
>
> I am using the following Log4j API to log messages at a configurable level:
> {code:java}
> logger.atLevel(level).log(...); {code}
> This works fine, but then a user configured the log level to be {{Level.OFF}}
> and to his surprise messages were still logged, at level {{OFF}}. This feels
> like a bug to me.
> I have created a small demo project that reproduces this behaviour at
> [https://github.com/breun/log4j-off]. This project logs these two messages:
> {code:java}
> INFO - Foo
> OFF - Foo {code}
> But I expected only the first of those two to get logged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
