But how would this filter be installed given that there is no configuration file? Aren't we back to a system property to install this filter?
On Tue, Jan 2, 2018 at 12:27 PM, Ralph Goers (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/LOG4J2-1944?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16307645#comment-16307645 ] > > Ralph Goers commented on LOG4J2-1944: > ------------------------------------- > > Rather than adding yet another system property to deal with this single > case it seems to me that allowing some sort of filtering on the message > text or log level in StatusLogger would be a more flexible solution to > this. This way the user could configure a filter that suppresses any status > logger message they don't want to see. > > > Should suppress message "ERROR No log4j2 configuration file found..." > when programmatic API is used to config log4j. > > ------------------------------------------------------------ > -------------------------------------------------------- > > > > Key: LOG4J2-1944 > > URL: https://issues.apache.org/jira/browse/LOG4J2-1944 > > Project: Log4j 2 > > Issue Type: Bug > > Components: Configurators > > Affects Versions: 2.6.2 > > Reporter: Weian Deng > > Priority: Minor > > Attachments: LOG4J2-1944.patch, LOG4J2_1944.zip > > > > > > Log4j can be configured through log4j's configuration API. There are > cases that an organization want to control the log4j configuration through > the configuration API and discourage the use of config file. The error > message > > {code} > > ERROR No log4j2 configuration file found. Using default configuration: > logging only errors to the console. > > {code} > > is misleading. > > Can this be downgraded to WARN message, or provide a way to suppress it? > > > > -- > This message was sent by Atlassian JIRA > (v6.4.14#64029) >
