【问题标题】:Change appender level instead of the logger level更改 appender 级别而不是 logger 级别
【发布时间】:2019-05-28 08:32:55
【问题描述】:

我的团队使用Spring Boot Admin 来控制我们的spring application
Spring Boot Admin 中,我们可以选择更改Runtime 中的logger 级别,

我们为每个task(Thread) 有一个单独的记录器,如果我们只想查看一个线程的控制台日志,我们关闭所有其他线程的记录器, 问题是每个记录器都为STDOUT 和某个文件发送它的输出,我们想关闭标准输出。

log4j2.xml 配置示例:

<Loggers>
   <Logger name="task1" level="info">
     <AppenderRef ref="Console"/>
     <AppenderRef ref="File"/>
   </Logger>
   <Logger name="task2" level="info">
     <AppenderRef ref="Console"/>
     <AppenderRef ref="File"/>
   </Logger>
</Loggers>

我们尝试了很多解决方案:

  • 使用结合可加性的父记录器,并将每个附加器分离到不同的记录器, 有什么想法吗?

【问题讨论】:

  • 您能否为控制台和文件附加程序添加单独的记录器?喜欢:
  • 可以添加任务/线程相关的代码吗?

标签: spring-boot log4j2 spring-boot-admin


【解决方案1】:

Log4j2 默认不允许管理 System.out 和 System.err 流。

为了阐明控制台记录器的工作原理: 只需 Console appender 将其输出打印到 System.out 或 System.err。根据文档,如果您默认不指定目标,它将打印到 System.out:

https://logging.apache.org/log4j/2.x/manual/appenders.html

目标 ||字符串 || “SYSTEM_OUT”或“SYSTEM_ERR”。默认为“SYSTEM_OUT”。


这是一个例子:

log4j2.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <Properties>
        <Property name="log-pattern">%d{ISO8601} %-5p %m\n</Property>
    </Properties>
    <appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout>
                <pattern>${log-pattern}</pattern>
            </PatternLayout>
        </Console>
    </appenders>
    <Loggers>
        <logger name="testLogger" level="info" additivity="false">
            <AppenderRef ref="Console"/>
        </logger>
    </Loggers>
</configuration>

LogApp.java

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

public class LogApp {
    public static void main(String[] args) {
        Logger log = LogManager.getLogger("testLogger");
        log.info("Logger output test!");
        System.out.println("System out test!");
    }
}

输出:

2019-01-08T19:08:57,587 INFO  Logger output test!
System out test!

管理系统流的解决方法

参加 Dmitry Pavlenko 的流重定向课程

https://sysgears.com/articles/how-to-redirect-stdout-and-stderr-writing-to-a-log4j-appender/

import org.apache.logging.log4j.Level;
import org.apache.logging.log4j.Logger;

import java.io.IOException;
import java.io.OutputStream;

/**
  * A change was made on the existing code:
  * - At (LoggingOutputStream#flush) method 'count' could contain 
  *  single space character, this types of logs has been skipped
  */
public class LoggingOutputStream extends OutputStream {
    private static final int DEFAULT_BUFFER_LENGTH = 2048;
    private boolean hasBeenClosed = false;
    private byte[] buf;
    private int count;

    private int curBufLength;

    private Logger log;

    private Level level;

    public LoggingOutputStream(final Logger log,
                               final Level level)
            throws IllegalArgumentException {
        if (log == null || level == null) {
            throw new IllegalArgumentException(
                    "Logger or log level must be not null");
        }
        this.log = log;
        this.level = level;
        curBufLength = DEFAULT_BUFFER_LENGTH;
        buf = new byte[curBufLength];
        count = 0;
    }

    public void write(final int b) throws IOException {
        if (hasBeenClosed) {
            throw new IOException("The stream has been closed.");
        }
        // don't log nulls
        if (b == 0) {
            return;
        }
        // would this be writing past the buffer?
        if (count == curBufLength) {
            // grow the buffer
            final int newBufLength = curBufLength +
                    DEFAULT_BUFFER_LENGTH;
            final byte[] newBuf = new byte[newBufLength];
            System.arraycopy(buf, 0, newBuf, 0, curBufLength);
            buf = newBuf;
            curBufLength = newBufLength;
        }

        buf[count] = (byte) b;
        count++;
    }

    public void flush() {
        if (count <= 1) {
            count = 0;
            return;
        }
        final byte[] bytes = new byte[count];
        System.arraycopy(buf, 0, bytes, 0, count);
        String str = new String(bytes);
        log.log(level, str);
        count = 0;
    }

    public void close() {
        flush();
        hasBeenClosed = true;
    }
}

并为系统输出流创建一个自定义记录器,而不是注册它。

这里是记录器使用的完整代码:

log4j2.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <Properties>
        <Property name="log-pattern">%d{ISO8601} %-5p %m\n</Property>
    </Properties>
    <appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout>
                <pattern>${log-pattern}</pattern>
            </PatternLayout>
        </Console>
    </appenders>
    <Loggers>
        <logger name="testLogger" level="info" additivity="false">
            <AppenderRef ref="Console"/>
        </logger>
        <logger name="systemOut" level="info" additivity="true"/>
    </Loggers>
</configuration>

SystemLogging.java

import org.apache.logging.log4j.Level;
import org.apache.logging.log4j.LogManager;

import java.io.PrintStream;

public class SystemLogging {
    public void enableOutStreamLogging() {
        System.setOut(createPrintStream("systemOut", Level.INFO));
    }

    private PrintStream createPrintStream(String name, Level level) {
        return new PrintStream(new LoggingOutputStream(LogManager.getLogger(name), level), true);
    }
}

LogApp.java

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

public class LogApp {
    public static void main(String[] args) {
        new SystemLogging().enableOutStreamLogging();

        Logger log = LogManager.getLogger("testLogger");
        log.info("Logger output test!");
        System.out.println("System out test!");
    }
}

最终输出

2019-01-08T19:30:43,456 INFO  Logger output test!
19:30:43.457 [main] INFO  systemOut - System out test!

现在,根据需要使用新的记录器配置自定义系统。

加号;如果您不想覆盖 System.out 并且只想保存它:TeeOutputStreamcommons-io 库中。您可以将原始System.out 替换为原始System.outLoggingOutputStream 的组合,这将同时写入两个流。这不会更改原始输出,但允许您使用日志记录附加程序保存 System.out

【讨论】:

    猜你喜欢
    • 2012-05-30
    • 2016-06-09
    • 2015-07-09
    • 1970-01-01
    • 1970-01-01
    • 2018-07-21
    • 2018-10-20
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多