FixedWindowRollingPolicy，SizeBasedTriggeringPolicy

[linuxdf]

logback, If the specified number of files is not generated according to the configured rules, the history log is automatically cleared;

The configuration is as follows:

<appender name="INFO_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>${LOGS_PATH}/info.log</file>
    <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
        <fileNamePattern>${LOGS_PATH}/info-%i.log.gz</fileNamePattern>
        <minIndex>1</minIndex>
        <maxIndex>30</maxIndex>


    </rollingPolicy>
    <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
        <maxFileSize>1024MB</maxFileSize>

    </triggeringPolicy>

    <encoder>
        <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} ${PID} [%thread] %-5level %logger{35} - %msg%n</pattern>
        <charset>UTF-8</charset>
    </encoder>
    <filter class="ch.qos.logback.classic.filter.LevelFilter">
        <level>INFO</level>
        <onMatch>ACCEPT</onMatch>
        <onMismatch>DENY</onMismatch>
    </filter>
</appender>

As shown below:

[linuxdf]

1024MB

Does this configuration limit the size of individual files or the overall log size.