Spring Rest基于Log4j2.xml按响应码动态调整日志级别咨询

针对你提出的需求——成功请求（响应码<400）仅保留WARN及以上级别日志，异常请求（响应码≥400）保留INFO及以上级别日志，且需异步缓冲日志以适配响应码未知的场景，以下是两种可行的实现方案：

方案一：MDC+自定义日志过滤器（基于SLF4J/Logback） #

利用日志框架的**映射诊断上下文（MDC）**存储动态日志阈值，配合自定义过滤器实现条件输出，这是最常用且轻量的方案。

步骤1：请求拦截器中动态设置MDC阈值 #

通过请求拦截器在请求开始时默认设置高阈值（仅输出WARN+），请求结束后根据响应码调整阈值：

public class ResponseCodeLogInterceptor implements HandlerInterceptor {
    @Override
    public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) {
        // 默认仅记录WARN及以上日志，避免成功请求产生冗余输出
        MDC.put("LOG_LEVEL_THRESHOLD", "WARN");
        return true;
    }

    @Override
    public void afterCompletion(HttpServletRequest request, HttpServletResponse response, Object handler, Exception ex) {
        int status = response.getStatus();
        if (status >= 400) {
            // 异常请求下调阈值，允许INFO及以上日志输出
            MDC.put("LOG_LEVEL_THRESHOLD", "INFO");
        }
        // 清理MDC，防止线程池复用导致上下文污染
        MDC.remove("LOG_LEVEL_THRESHOLD");
    }
}

步骤2：自定义Logback过滤器 #

实现过滤器读取MDC中的阈值，判断是否输出日志：

import ch.qos.logback.classic.Level;
import ch.qos.logback.classic.spi.ILoggingEvent;
import ch.qos.logback.core.filter.Filter;
import ch.qos.logback.core.spi.FilterReply;

public class DynamicThresholdFilter extends Filter<ILoggingEvent> {
    @Override
    public FilterReply decide(ILoggingEvent event) {
        String thresholdStr = event.getMDCPropertyMap().get("LOG_LEVEL_THRESHOLD");
        Level threshold = thresholdStr != null ? Level.toLevel(thresholdStr) : Level.WARN;
        
        return event.getLevel().isGreaterOrEqual(threshold) ? FilterReply.ACCEPT : FilterReply.DENY;
    }
}

步骤3：Logback配置文件 #

将自定义过滤器绑定到Appender：

<configuration>
    <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
        <!-- 绑定自定义动态阈值过滤器 -->
        <filter class="com.yourpackage.DynamicThresholdFilter"/>
        <encoder>
            <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </encoder>
    </appender>

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

注意事项 #

• 若使用异步Appender，需开启MDC复制：在<asyncAppender>中添加<includeCallerData>true</includeCallerData>，确保异步线程能获取到请求线程的MDC上下文。
• 必须在请求结束后清理MDC，避免线程池复用导致后续请求继承旧的阈值。

方案二：请求作用域日志缓冲器 #

通过ThreadLocal在请求生命周期内缓冲所有日志事件，请求结束时根据响应码筛选输出，适合需要完全控制日志输出时机的场景。

步骤1：实现请求作用域日志缓冲工具类 #

import ch.qos.logback.classic.Logger;
import ch.qos.logback.classic.LoggerContext;
import ch.qos.logback.classic.Level;
import ch.qos.logback.classic.spi.ILoggingEvent;
import org.slf4j.LoggerFactory;
import java.util.ArrayList;
import java.util.List;

public class RequestScopedLogBuffer {
    private static final ThreadLocal<List<ILoggingEvent>> LOG_BUFFER = new ThreadLocal<>();

    public static void addLogEvent(ILoggingEvent event) {
        List<ILoggingEvent> buffer = LOG_BUFFER.get();
        if (buffer == null) {
            buffer = new ArrayList<>();
            LOG_BUFFER.set(buffer);
        }
        buffer.add(event);
    }

    public static void flush(int responseCode) {
        List<ILoggingEvent> buffer = LOG_BUFFER.get();
        if (buffer == null) return;

        Level threshold = responseCode >= 400 ? Level.INFO : Level.WARN;
        LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory();
        
        for (ILoggingEvent event : buffer) {
            if (event.getLevel().isGreaterOrEqual(threshold)) {
                Logger logger = loggerContext.getLogger(event.getLoggerName());
                logger.callAppenders(event);
            }
        }
        LOG_BUFFER.remove();
    }
}

步骤2：自定义缓冲Appender #

将日志事件转发到缓冲工具类：

import ch.qos.logback.classic.spi.ILoggingEvent;
import ch.qos.logback.core.AppenderBase;

public class BufferingAppender extends AppenderBase<ILoggingEvent> {
    @Override
    protected void append(ILoggingEvent event) {
        RequestScopedLogBuffer.addLogEvent(event);
    }
}

步骤3：拦截器中触发日志刷新 #

public class LogFlushInterceptor implements HandlerInterceptor {
    @Override
    public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) {
        // 清理旧缓冲，避免线程复用污染
        RequestScopedLogBuffer.LOG_BUFFER.remove();
        return true;
    }

    @Override
    public void afterCompletion(HttpServletRequest request, HttpServletResponse response, Object handler, Exception ex) {
        RequestScopedLogBuffer.flush(response.getStatus());
    }
}

步骤4：Logback配置 #

<configuration>
    <appender name="BUFFER" class="com.yourpackage.BufferingAppender"/>

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

优缺点 #

• 优点：完全控制日志输出时机，支持复杂的筛选逻辑；
• 缺点：高并发场景下可能占用较多内存，需注意缓冲大小限制。

内容的提问来源于stack exchange，提问作者Arun Gopalpuri