[
https://issues.apache.org/jira/browse/LOG4J2-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478005#comment-17478005
]
Ralph Goers edited comment on LOG4J2-3340 at 1/18/22, 4:05 PM:
---------------------------------------------------------------
The StatusLogger initializes with the SimpleLogger as the default. When a
configuration takes place a Listener gets registered. So we have a default
logging level for the SimpleLogger (default logging) and we have a level that
filters whether an event is sent to a listener.
Think of it as if the SimpleLogger is the Root Logger with a hard-wired
appender. You are setting the logging level of the Root Logger. Listeners are
similar to separate Appenders where each has its own Level filter.
So if listeners are present events are sent to them. If they are not then the
Root Logger is used. This really isn't much different than a normal logging
config except you can't see the XML configuration.
was (Author: [email protected]):
The StatusLogger initializes with the SimpleLogger as the default. When a
configuration takes place a Listener gets registered. So we have a default
logging level for the SimpleLogger (default logging) and we have a level that
filters whether an event is sent to a listener.
Think of it as if the SimpleLogger is the Root Logger with a hard-wired
appender. You are setting the logging level of the Root Logger. Listeners are
similar to separate Appenders where each has its own Level filter.
> StatusLogger's log Level cannot be changed as advertised
> --------------------------------------------------------
>
> Key: LOG4J2-3340
> URL: https://issues.apache.org/jira/browse/LOG4J2-3340
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Michael Vorburger
> Assignee: Gary D. Gregory
> Priority: Major
> Fix For: 2.17.2
>
>
> I would like to see the warn log from {{LogManager}} re. which implementation
> it picked, if multiple.
> I would like to be able to do this without a system property but using a
> properties file on the classpath.
> StatusLogger's JavaDoc (currently) says that "This can be overridden via a
> system property named #DEFAULT_STATUS_LISTENER_LEVEL and will work with any
> Log4j provider.", where DEFAULT_STATUS_LISTENER_LEVEL is
> "log4j2.StatusLogger.level".
> However that currently doesn't seem to quite work as advertised. (If you
> think it does, please suggest how.) I can see some stuff in StatusLogger
> related to its default log level been (only?) for StatusListener and
> StatusData? This seems confusing.
> I'll raise a PR with a proposed simple fix for this for your review.
> [~ckozak] / [~ggregory]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
