我要将我的java应用程序放入docker中。但基于我们公司的测井设施,我必须使用fluentd
收集容器'登录。这要求我将java stacktraces放入一行日志中。
我做了以下工作,它在某些情况下有效但彼此失败。
package com.alex;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import java.util.zip.DataFormatException;
public class Main {
private static final Logger logger = LoggerFactory.getLogger(Main.class);
public static void alexExc() throws Exception {
throw new Exception("hello");
}
public static void main(String[] args) throws Exception {
try {
alexExc();
} catch (Throwable t) {
logger.error("oops", t);
}
throw new DataFormatException("invalid data format");
}
}
以下是我的转换器用我指定的转换器替换分隔符"#012"
package com.alex;
import ch.qos.logback.classic.pattern.ThrowableProxyConverter;
import ch.qos.logback.classic.spi.IThrowableProxy;
import ch.qos.logback.core.CoreConstants;
public class OneLineStackTraceConverter extends ThrowableProxyConverter {
protected String throwableProxyToString(IThrowableProxy tp) {
String originalStackTrace = super.throwableProxyToString(tp);
return originalStackTrace.replace(CoreConstants.LINE_SEPARATOR, " #012");
}
}
然后是我的logback配置:
<?xml version="1.0" encoding="UTF-8" ?>
<configuration scan="true" scanPeriod="30 seconds">
<conversionRule conversionWord="ex"
converterClass="com.alex.OneLineStackTraceConverter" />
<appender name="INFO_FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/logs/loggingmdc/info.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>/logs/loggingmdc/info.log.%i</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>5</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>1GB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %le %logger{0}: ## %msg\n</pattern>
</encoder>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>INFO</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
</appender>
<appender name="DEBUG_FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/logs/loggingmdc/debug.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>/logs/loggingmdc/debug.log.%i</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>5</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>1GB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %le %logger{0}: ## %msg %ex\n</pattern>
</encoder>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>DEBUG</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
</appender>
<appender name="ERROR_FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/logs/loggingmdc/error.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>/logs/loggingmdc/error.log.%i</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>5</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>1GB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %le %logger{0}: ## %msg %ex\n</pattern>
</encoder>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>ERROR</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
</appender>
<appender name="THIRD_PARTY_FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/logs/loggingmdc/thirdparty.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>/logs/loggingmdc/thirdparty.log.%i</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>5</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>1GB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %le %logger{0}: ## %msg %ex\n</pattern>
</encoder>
</appender>
<root level="INFO">
<appender-ref ref="THIRD_PARTY_FILE"/>
</root>
<logger name="com.alex" level="DEBUG" additivity="false">
<appender-ref ref="INFO_FILE"/>
<appender-ref ref="DEBUG_FILE"/>
<appender-ref ref="ERROR_FILE"/>
</logger>
</configuration>
正如您在我的回溯配置中所看到的,我添加了conversionRule
来指定记录事件中的异常是使用我的OneLineStackTraceConverter
。
%ex
,它都可以使用%ex
,它就不起作用。为什么?如果用户忘记在其模式中包含%ex
,我是否还有其他一些convertWord用于该异常?DataFormatException
没有进入日志文件,它出现在控制台中,我也希望它转到日志文件。我怎么能这样做呢?感谢。
答案 0 :(得分:2)
如果我不在模式中包含%ex,它就不起作用。为什么呢?
因为您声明了转换字= ex
。如果你不使用它,Logback不知道你的想法,所以它什么都不做。将此与在代码中声明变量而不使用它进行比较,您应该能够理解。
最后一次DataFormatException没有转到日志文件
因为您的代码没有记录。如果在代码中抛出异常,Logback(或者你的SLF4J)将不会自动捕获并记录它。