2.0.1 新特性介绍: 在日志中记录trace id
java-chassis 使用 MDC 的方式记录 trace id, 可以在 log4j2 或者 logback 中打印 trace id。 java-chassis 记录 trace id 增加 了 Marker , 开发者可以方便的将这类日志进行分类输出。
log4j2的配置如下:
<Console name="Console" target="SYSTEM_OUT">
<MarkerFilter marker="SERVICECOMB_MARKER" onMatch="DENY" onMismatch="ACCEPT"/>
<PatternLayout pattern="[%d][%t][%p][%c:%L] %m%n"/>
</Console>
<Console name="Console-Tracing" target="SYSTEM_OUT">
<MarkerFilter marker="SERVICECOMB_MARKER" onMismatch="DENY" onMatch="ACCEPT"/>
<PatternLayout pattern="[%d][%t][%p][%c:%L][%X{SERVICECOMB_TRACE_ID}] %m%n"/>
</Console>
</Appenders>
logback的配置如下:
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d [%level] [%thread][%X{SERVICECOMB_TRACE_ID}] - %msg (%F:%L\)%n</pattern>
</appender>
结合 Marker, 可以将日志分类显示:
业务日志包含 trace id
- 记录 access log
private static final Logger LOGGER
= LoggerFactory.getLogger(AccessLogHandler.class);
@Override
public void handle(Invocation invocation, AsyncResponse asyncResp) throws Exception {
invocation.getTraceIdLogger().info(LOGGER, "request for operation {} begin", invocation.getInvocationQualifiedName());
invocation.next((resp) -> {
invocation.getTraceIdLogger().info(LOGGER, "request for operation {} end", invocation.getInvocationQualifiedName());
asyncResp.complete(resp);
});
}
}
配置 Handler
<handler id="custom-access-log"
</config>
启用 Handler
- 业务日志
public class RegisterUrlPrefixEndpoint {
private static final Logger LOGGER
= LoggerFactory.getLogger(RegisterUrlPrefixEndpoint.class);
@GetMapping(path = "/getName")
public String getName(@RequestParam(name = "name") String name) {
((Invocation) ContextUtils.getInvocationContext()).getTraceIdLogger().info(LOGGER, "get name invoked.");
return name;
}
}
增加了 access log 和业务日志后的效果如下:
[5e72e39e55209533-1] - request for operation PRODUCER rest demo-register-url-prefix-server.RegisterUrlPrefixEndpoint.getName begin
[5e72e39e55209533-1] - request for operation PRODUCER rest demo-register-url-prefix-server.RegisterUrlPrefixEndpoint.getName end