Logback different packages (business logs) are output to different log files

One of the main purposes of logging is to easily find the cause of the problem when there is a problem , But sometimes too many logs will also cause a lot of disk space , Therefore, appropriate log storage configuration is required . 

A feasible method is to target different log types , Configure a separate log storage policy , Include the file name , Rolling strategy and maximum number of logs .

1. Define log output file

<!--  Business log output  -->
    <appender name="biz_info" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>${log.path}/biz_info.log</file>
        <!--  Circular policy ： Create log files based on time  -->
        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <!--  Log file name format  -->
            <fileNamePattern>${log.path}/biz-info.%d{yyyy-MM-dd}.log</fileNamePattern>
            <!--  Maximum log retention  60 individual  -->
            <maxHistory>60</maxHistory>
            <cleanHistoryOnStart>true</cleanHistoryOnStart>
        </rollingPolicy>
        <encoder>
            <pattern>${log.pattern}</pattern>
        </encoder>
        <filter class="ch.qos.logback.classic.filter.LevelFilter">
            <!--  Level of filtering  -->
            <level>INFO</level>
            <!--  Operation when matching ： receive （ Record ） -->
            <onMatch>ACCEPT</onMatch>
            <!--  Operation in case of mismatch ： Refuse （ Don't record ） -->
            <onMismatch>DENY</onMismatch>
        </filter>
    </appender>

maxHistory: Parameter indicates the maximum number of reserved log files  

{yyyy-MM-dd}: The parameter indicates that the file is divided by day ,{yyyy-MM-dd-HH} Indicates that the file is split by hour . Because the string formatted by time is different from the previous string , Then regenerate a file . At this time, the generated file name , There needs to be more -%i

cleanHistoryOnStart: Set to true, It means to clear redundant logs when starting .

<!--  Business log output  -->
    <appender name="biz_info" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>${log.path}/biz_info.log</file>
        <!--  Circular policy ： Create log files based on time  -->
        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <!--  Log file name format  -->
            <fileNamePattern>${log.path}/biz-info.%d{yyyy-MM-dd}-%i.log</fileNamePattern>
            <!--  Maximum log retention  60 individual  -->
            <maxHistory>60</maxHistory>
            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                <maxFileSize>100MB</maxFileSize>
            </timeBasedFileNamingAndTriggeringPolicy>
        </rollingPolicy>
        <encoder>
            <pattern>${log.pattern}</pattern>
        </encoder>
        <filter class="ch.qos.logback.classic.filter.LevelFilter">
            <!--  Level of filtering  -->
            <level>INFO</level>
            <!--  Operation when matching ： receive （ Record ） -->
            <onMatch>ACCEPT</onMatch>
            <!--  Operation in case of mismatch ： Refuse （ Don't record ） -->
            <onMismatch>DENY</onMismatch>
        </filter>
    </appender>

 timeBasedFileNamingAndTriggeringPolicy： Divide by file size .

2. Definition logger 

<!-- Business log -->
    <logger name="biz_info" level="info" additivity="false">
        <appender-ref ref="biz_info"/>
    </logger>

 additivity="false" Indicates that the log here is not written root Corresponding logger.

3. Definition logger Variable

private static final Logger log = LoggerFactory.getLogger("biz_info");

Classes that need logging , Definition logger Variable . 

4. Log

log.info(" The list shows ");

Just record the log in the normal way .