You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/01/18 13:08:00 UTC
[jira] [Assigned] (LOG4J2-3340) StatusLogger's log Level cannot be changed as advertised
[ https://issues.apache.org/jira/browse/LOG4J2-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory reassigned LOG4J2-3340:
---------------------------------------
Assignee: Gary D. Gregory
> 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)