[jira] [Updated] (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
]
Matt Sicker updated LOG4J2-3340:
Fix Version/s: 2.18.1
(was: 2.18.0)
> 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.18.1
>
>
> 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.10#820010)
[jira] [Updated] (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
]
Volkan Yazici updated LOG4J2-3340:
--
Fix Version/s: 2.18.0
(was: 2.17.3)
> 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.18.0
>
>
> 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.7#820007)
[jira] [Updated] (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 updated LOG4J2-3340:
Fix Version/s: 2.17.3
(was: 2.17.2)
> 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.3
>
>
> 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)
[jira] [Updated] (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
]
Michael Vorburger updated LOG4J2-3340:
--
Description:
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]
was:
I would like to see the warn log from {{LogManager}} re. which implementation
it picked, it 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]
> 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
>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)
