零侵入 · 防爆炸 · 生产级
适用:Kubernetes 1.20+ / 裸机 / 容器混合场景
目标:业务输出单行 JSON,采集层(Promtail / Vector)负责解析、采样、标签与告警,尽量降低业务代码改动与系统资源消耗。
Vector 替代 Promtail 做解析以节省 CPU/内存。建议业务输出单行 JSON(最小必需字段):
{
"ts":"2026-01-23T14:23:45.123Z",
"level":"INFO|WARN|ERROR",
"logger":"c.x.Foo",
"msg":"...",
"traceId":"a1b2c3",
"uri":"/api/order",
"duration":120,
"userId":123456,
"event":"order_create|login|APP_START|security|slow_sql",
"error":"NullPointerException: xxx"
}
说明:
error=""duration>500(ms)event 字段区分注意:不要将高基数字段(如 userId、orderId)作为标签。
logback 配置与 common-logging 模块统一下发,业务只需引入一次依赖并使用简单 wrapper(如 AppLogger.info(...))。traceId、uri、startTime、userId,请求结束时写入 duration 并清理。示例:Async JSON appender(logback)
<appender name="JSON" class="ch.qos.logback.core.ConsoleAppender">
<encoder class="net.logstash.logback.encoder.LogstashEncoder">
<includeContext>true</includeContext>
<provider class="net.logstash.logback.composite.loggingevent.LoggingEventPatternJsonProvider">
<pattern>{"ts":"%d{yyyy-MM-dd'T'HH:mm:ss.SSS'Z'}","level":"%level","logger":"%logger","msg":"%msg","traceId":"%X{traceId:-}","uri":"%X{uri:-}","duration":"%X{duration:-0}","userId":"%X{userId:-}","event":"%X{event:-}","error":"%X{error:-}"}</pattern>
</provider>
</encoder>
</appender>
<appender name="ASYNC_JSON" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="JSON" />
</appender>
<root level="INFO"><appender-ref ref="ASYNC_JSON"/></root>
Servlet Filter(伪码)
public class LoggingFilter implements Filter {
public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain) {
String traceId = extractOrGenerate(req);
MDC.put("traceId", traceId);
MDC.put("uri", ((HttpServletRequest)req).getRequestURI());
long start = System.currentTimeMillis();
try { chain.doFilter(req, res); }
finally {
MDC.put("duration", String.valueOf(System.currentTimeMillis() - start));
MDC.remove("traceId"); MDC.remove("uri"); MDC.remove("duration");
}
}
}