springboot中怎么进行统一日志处理？

逃离我推掉我的手 2023-10-03 19:24 63阅读 0赞

## 一.springboot的日志级别 ##

日志级别从低到高有：OFF、FATAL、ERROR、WARN、INFO、DEBUG、ALL

高级别包含了低级别，级别越高打印信息越先详细，默认情况下，spring boot从控制台打印出来的日志级别为INFO级别,设置如下

logging:
      level:
        root: warn # 设置日志级别为警告

此时的日志只能输出到控制台，输出不到文件中

## 二.Logback日志的详细使用 ##

如果我们想将日志输出到文件中，可以使用Logback日志，spring boot内部使用Logback作为日志实现的框架。

**使用步骤：**

（1）删除yaml中其它日志的配置以及我们设置的日志级别

（2）resources下创建logback-spring.xml文件，在xml中可以配置日志级别、日志输出位置等信息

<?xml version="1.0" encoding="UTF-8"?>
    <configuration  scan="true" scanPeriod="10 seconds">
        
        
        
        
    
        <contextName>logback</contextName>
        
        <property name="log.path" value="D:/guli_log/edu" />
    
        
        
        
        
        
        
        
        <property name="CONSOLE_LOG_PATTERN"
                  value="%yellow(%date{yyyy-MM-dd HH:mm:ss}) |%highlight(%-5level) |%blue(%thread) |%blue(%file:%line) |%green(%logger) |%cyan(%msg%n)"/>
    
    
        
        <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
            
            
            <filter class="ch.qos.logback.classic.filter.ThresholdFilter">
                <level>INFO</level>
            </filter>
            <encoder>
                <Pattern>${CONSOLE_LOG_PATTERN}</Pattern>
                
                <charset>UTF-8</charset>
            </encoder>
        </appender>
    
    
        
    
        
        <appender name="INFO_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
            
            <file>${log.path}/log_info.log</file>
            
            <encoder>
                <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
                <charset>UTF-8</charset>
            </encoder>
            
            <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
                
                <fileNamePattern>${log.path}/info/log-info-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
                <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                    <maxFileSize>100MB</maxFileSize>
                </timeBasedFileNamingAndTriggeringPolicy>
                
                <maxHistory>15</maxHistory>
            </rollingPolicy>
            
            <filter class="ch.qos.logback.classic.filter.LevelFilter">
                <level>INFO</level>
                <onMatch>ACCEPT</onMatch>
                <onMismatch>DENY</onMismatch>
            </filter>
        </appender>
    
        
        <appender name="WARN_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
            
            <file>${log.path}/log_warn.log</file>
            
            <encoder>
                <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
                <charset>UTF-8</charset> 
            </encoder>
            
            <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
                <fileNamePattern>${log.path}/warn/log-warn-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
                <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                    <maxFileSize>100MB</maxFileSize>
                </timeBasedFileNamingAndTriggeringPolicy>
                
                <maxHistory>15</maxHistory>
            </rollingPolicy>
            
            <filter class="ch.qos.logback.classic.filter.LevelFilter">
                <level>warn</level>
                <onMatch>ACCEPT</onMatch>
                <onMismatch>DENY</onMismatch>
            </filter>
        </appender>
    
    
        
        <appender name="ERROR_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
            
            <file>${log.path}/log_error.log</file>
            
            <encoder>
                <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
                <charset>UTF-8</charset> 
            </encoder>
            
            <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
                <fileNamePattern>${log.path}/error/log-error-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
                <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                    <maxFileSize>100MB</maxFileSize>
                </timeBasedFileNamingAndTriggeringPolicy>
                
                <maxHistory>15</maxHistory>
            </rollingPolicy>
            
            <filter class="ch.qos.logback.classic.filter.LevelFilter">
                <level>ERROR</level>
                <onMatch>ACCEPT</onMatch>
                <onMismatch>DENY</onMismatch>
            </filter>
        </appender>
    
        
        
        
        <springProfile name="dev">
            
            <logger name="com.guli" level="INFO" />
    
            
            <root level="INFO">
                <appender-ref ref="CONSOLE" />
                <appender-ref ref="INFO_FILE" />
                <appender-ref ref="WARN_FILE" />
                <appender-ref ref="ERROR_FILE" />
            </root>
        </springProfile>
    
    
        
        <springProfile name="pro">
    
            <root level="INFO">
                <appender-ref ref="CONSOLE" />
                <appender-ref ref="DEBUG_FILE" />
                <appender-ref ref="INFO_FILE" />
                <appender-ref ref="ERROR_FILE" />
                <appender-ref ref="WARN_FILE" />
            </root>
        </springProfile>
    
    </configuration>

启动类后，指定的输入日志路径会出现三个log文件，springboot的运行日志会出现在log\_info.log文件中，但错误日志信息默认不会输入到文件中

![7a8efd8234914c96a67370f5f3719377.png][]

(3)若想将错误日志输出到文件中，则需要

给全局异常类加上@slf4j注解，然后在全局异常处理方法中编写

log.要输出到的日志(e.getMessage)；

@ControllerAdvice
    @Slf4j
    public class GlobalExceptionHandler {
        //自定义异常
        @ResponseBody
        @ExceptionHandler(GuLiException.class)
        public R error(GuLiException e){
            e.printStackTrace();
            log.info(e.getMsg());
            return R.error().
                    code(e.getCode()).
                    message(e.getMsg());
        }
    }

此时只出现一行错误信息，并不详细

![4c5172e5187c45afacb280d041676278.png][]

（4）若想输出更详细的错误日志到文件中，则要利用工具类

public class ExceptionUtil {
    
        public static String getMessage(Exception e) {
            StringWriter sw = null;
            PrintWriter pw = null;
            try {
                sw = new StringWriter();
                pw = new PrintWriter(sw);
                // 将出错的栈信息输出到printWriter中
                e.printStackTrace(pw);
                pw.flush();
                sw.flush();
            } finally {
                if (sw != null) {
                    try {
                        sw.close();
                    } catch (IOException e1) {
                        e1.printStackTrace();
                    }
                }
                if (pw != null) {
                    pw.close();
                }
            }
            return sw.toString();
        }
    }

调用工具类getMessage方法

log.error(ExceptionUtil.getMessage(e));

全局异常处理类中创建一个toString()方法

@Override
    public String toString() {
        return "GuliException{" +
            "message=" + this.getMessage() +
            ", code=" + code +
            '}';
    }

[7a8efd8234914c96a67370f5f3719377.png]: https://img-blog.csdnimg.cn/7a8efd8234914c96a67370f5f3719377.png
[4c5172e5187c45afacb280d041676278.png]: https://img-blog.csdnimg.cn/4c5172e5187c45afacb280d041676278.png