Log4j2 Filter particular level in apender

Question

What filter should i use, to define particular level to be logged with apender? For example:

java:

LOGGER.debug("Debug message");
LOGGER.info("Info message");
LOGGER.warn("Warn message");
LOGGER.error("Error message");
LOGGER.fatal("Fatal message");

log4j2.xml:

<Configuration>
    <Appenders>
        <Console name="info-stdout-message">
            <PatternLayout pattern="[%logger{36}] %message %n" />
            <ThresholdFilter level="info"/>
        </Console>

        <Console name="detailed-stdout-message">
            <PatternLayout pattern="[%logger{36}] [%level] %message %n" />
        </Console>

        <File name="file-appender" fileName="logs/debug.log">
            <PatternLayout pattern="%d{HH:mm:ss dd.mm} [%t] [%-5level] %logger{36} - %msg %n" />
        </File>
    </Appenders>

    <Loggers>
        <Root level="debug">
            <AppenderRef ref="file-appender" level="debug" />
            <AppenderRef ref="info-stdout-message" level="info"/>
            <AppenderRef ref="detailed-stdout-message" level="info"/>
        </Root>
    </Loggers>
</Configuration>

The file output is fine, but in console I have such result:

[application.Main] [INFO] Info message
[application.Main] Info message
[application.Main] [WARN] Warn message
[application.Main] Warn message
[application.Main] [ERROR] Error message
[application.Main] Error message
[application.Main] [FATAL] Fatal message
[application.Main] Fatal message

but I need info-stdout-message appender to output only INFO messages, while detailed-stdout-message to output all EXEPT INFO. So the console output should looks like:

[application.Main] Info message
[application.Main] [WARN] Warn message
[application.Main] [ERROR] Error message
[application.Main] [FATAL] Fatal message

Can't find out how to prevent filters respect level inheritance. Is it possible to do this?

score 23 · Answer 1 · answered Nov 01 '14 at 18:31

Here two console appenders. One logs all trace, debug and info levels to std_out, the other logs all warn, error and fatal levels to std_err. This is very useful e.g. within eclipse since std_err is displayed red.

<Console name="STDOUT" target="SYSTEM_OUT">
    <PatternLayout pattern="%d{HH:mm:ss.SSS} (%6r) %-5p [%-7t] %F:%L %x - %m%n" />
    <Filters>
        <ThresholdFilter level="warn" onMatch="DENY" onMismatch="ACCEPT" />
    </Filters>
</Console>

<Console name="STDERR" target="SYSTEM_ERR">
    <PatternLayout pattern="%d{HH:mm:ss.SSS} (%6r) %-5p [%-7t] %F:%L %x - %m%n" />
    <Filters>
        <ThresholdFilter level="WARN" onMatch="ACCEPT" />
    </Filters>
</Console>

score 20 · Accepted Answer · edited Oct 17 '18 at 14:44

This works:

<Console name="info-stdout-message">
    <PatternLayout pattern="[%logger{36}] %message %n" />
    <Filters>

        <!-- Now deny warn, error and fatal messages -->
        <ThresholdFilter level="warn"  onMatch="DENY"   onMismatch="NEUTRAL"/>

        <!-- This filter accepts info, warn, error, fatal and denies debug/trace -->
        <ThresholdFilter level="info"  onMatch="ACCEPT" onMismatch="DENY"/>
    </Filters>
</Console>

score 6 · Answer 3 · answered Sep 05 '16 at 10:43

It took me very long to figure out how to filter a range of LogLevels via the log4j2.xml configuration file. In the End this worked for me :

<Filters>
    <ThresholdFilter level="trace" />
    <ThresholdFilter level="info" onMatch="DENY" onMismatch="NEUTRAL" />
</Filters>

In this case Log4J will log all messages from Level.TRACE to Level.DEBUG, all levels below Level.DEBUG will be ignored.

Cristian Florescu · Answer 4 · 2017-02-18T13:04:30.577

Please check all log4j2 filtering possibilities at https://logging.apache.org/log4j/2.0/manual/filters.html

Sample configuration fragment

...    
<Console name="DEFAULT" target="SYSTEM_OUT">
    <PatternLayout>
        <Pattern>[%d][%p][%c:%L:%M] - %m%n</Pattern>
    </PatternLayout>
    <Filters>
        <RegexFilter regex="(?s).*(sql01|sql02|sql03).*" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Filters>
</Console>
...

score 1 · Answer 5 · answered Feb 18 '17 at 17:25

Actually, from your question it looks like you don't want two different appenders, but two different patterns that are using under different circumstances. For that you should just use a PatternSelector.

    <Console name="stdout-message">
      <ScriptPatternSelector defaultPattern="[%logger{36}] [%level] %message %n">
        <Script name="BeanShellSelector" language="bsh"><![CDATA[
          if (logEvent.getLevel() == Level.INFO) {
            return "INFO";
          } else {
            return null;
          }]]>
        </Script>
        <PatternMatch key="INFO" pattern="[%logger{36}] %message %n"/>
       </ScriptPatternSelector>
    </Console>

Bathri Nathan · Answer 6 · 2022-12-17T17:32:09.323

Here is the Log4j2 config to ignore "warn" logs only for docxj4. check out the code below. thanks in advance.

<configuration>

<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel"/>

<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">

    <filter class="ch.qos.logback.classic.filter.LevelFilter">
        <level>WARN</level>
        <onMatch>DENY</onMatch>
        <onMismatch>NEUTRAL</onMismatch>
    </filter>

    <encoder>
        <pattern>%date %coloredLevel %logger{15} - %message%n%xException{10}</pattern>
    </encoder>
</appender>

<appender name="FILE" class="ch.qos.logback.core.FileAppender">

    <filter class="ch.qos.logback.classic.filter.LevelFilter">
        <level>WARN</level>
        <onMatch>DENY</onMatch>
        <onMismatch>NEUTRAL</onMismatch>
    </filter>

    <file>${application.home:-.}/logs/application.log</file>
    <encoder>
        <pattern>%date [%level] from %logger in %thread - %message%n%xException</pattern>
    </encoder>
</appender>

<logger name="org.docx4j" level="INFO"/>

<root level="INFO">
    <appender-ref ref="STDOUT"/>
    <appender-ref ref="FILE"/>
</root>
</configuration>

The question asked about Log4j2 Core, you are giving a solution for Logback. — Piotr P. Karwasz, Dec 16 '22 at 16:36
@PiotrP.Karwasz I have shared the configuration for Log4j2 to ignore "warn" logs specifically for docx4j. — Bathri Nathan, Dec 17 '22 at 17:34

score 0 · Answer 7 · answered Dec 16 '22 at 17:07

While all these workarounds were necessary in 2014, when the question was posted:

in version 2.4 a LevelRangeFilter was introduced (cf. LOG4J2-1106), which allows to write:
```
<LevelRangeFilter minLevel="INFO" maxLevel="INFO"/>
```
to select only INFO messages or:
```
<LevelRangeFilter minLevel="WARN" maxLevel="INFO"/>
```
to select a range (from most to least specific level).

version 2.13.0 saw the appearance of a LevelMatchFilter that further simplifies the configuration:
```
<LevelMatchFilter level="INFO"/>
```

Log4j2 Filter particular level in apender

7 Answers7

Linked