1、低版本sleuth会默认启用一个tomcat级别的过滤器:ExceptionLoggingFilter
源码如下:
class ExceptionLoggingFilter implements Filter {
private static final Log log = LogFactory.getLog(ExceptionLoggingFilter.class);
@Override public void init(FilterConfig filterConfig) throws ServletException {
}
@Override public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain) throws IOException, ServletException {
try {
chain.doFilter(request, response);
} catch (Exception e) {
if (log.isErrorEnabled()) {
log.error("Uncaught exception thrown", e);
}
throw e;
}
}
@Override public void destroy() {
}
}
问题:
这个过滤器会打印ERROR级别的日志,企业告警配置一般都是以ERROR级别日志为准,所以会因此打很多告警电话,就这个代码让我每天凌晨3~5点起床排查,持续了快两周
出现场景:
低版本sleuth,例如2.0.4.RELEASE版本。
处理方案1:
如果不得不用低版本sleuth(主要为了兼容jdk8和低版本springBoot):官方支持该配置禁用自带过滤器,默认是true,改成false再自己实现以下:
1.禁用官方的:
spring.sleuth.web.exception-throwing-filter-enabled=false
2.自己实现:
启动类上加@ServletComponentScan注解。然后新增以下配置类
@WebFilter("/*")
public class ExceptionLogFilter implements Filter {
private static final Log log = LogFactory.getLog(ExceptionLogFilter.class);
@Override public void init(FilterConfig filterConfig) throws ServletException {
}
@Override public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain) throws IOException, ServletException {
try {
chain.doFilter(request, response);
} catch (Exception ex) {
log.warn("EX >>>>>> Uncaught exception thrown:{}", ex);
}
}
@Override public void destroy() {
}
}
处理方案2:
换成高版本sleuth,官方默认删除了这个类,比如3.1.1版本的