Spring Boot中日誌每日分割

時間 2019-11-13

原文原文鏈接

問題

想使用Spring Boot中日誌輸出，這樣之後遇到問題，就能夠翻看日誌數據，看看程序運行的過程，便於排查錯誤。html

logback基礎配置

logback-spring.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <include resource="org/springframework/boot/logging/logback/defaults.xml" />
    <property name="LOG_FILE" value="${LOG_FILE:-${LOG_PATH:-${LOG_TEMP:-${java.io.tmpdir:-/tmp}}/}spring.log}"/>
    <include resource="org/springframework/boot/logging/logback/console-appender.xml" />
    <include resource="org/springframework/boot/logging/logback/file-appender.xml" />
    <root level="INFO">
        <appender-ref ref="CONSOLE" />
        <appender-ref ref="FILE" />
    </root>
</configuration>

application.properties

logging.path=logs

上面兩步，主要就是對spring-boot對最基礎日誌配置。java

按日期分割

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
	<include resource="org/springframework/boot/logging/logback/defaults.xml" />
	<property name="LOG_FILE"
		value="${LOG_FILE:-${LOG_PATH:-${LOG_TEMP:-${java.io.tmpdir:-/tmp}}/}spring.log}" />
	<include
		resource="org/springframework/boot/logging/logback/console-appender.xml" />
	<appender name="DAY_FILE"
		class="ch.qos.logback.core.rolling.RollingFileAppender">
		<encoder>
			<pattern>${FILE_LOG_PATTERN}</pattern>
		</encoder>
		<file>${LOG_FILE}</file>
		<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
			<fileNamePattern>${LOG_FILE}.%d{yyyy-MM-dd_HH-mm}.log</fileNamePattern>
			<maxHistory>365</maxHistory>
		</rollingPolicy>
	</appender>
	<root level="INFO">
		<appender-ref ref="CONSOLE" />
		<appender-ref ref="DAY_FILE" />
	</root>
</configuration>

**Note:**這裏的DAY_FILE，其實主要就是參考org/springframework/boot/logging/logback/file-appender.xml進行配置。spring

Java代碼調用

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;


public class DemoController {
	private final static Logger logger = LoggerFactory.getLogger(DemoController.class);

    public Demo greeting(@RequestParam(value="serviceId", defaultValue="World") String serviceId) {
    		logger.info("serviceId-->" + serviceId);
    		...
    }
}