<configuration>
    <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>../logs/CTRL_log.log</file>
<!--        <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">-->
<!--            <fileNamePattern>../logs/CTRL_log.log.%i.log</fileNamePattern>-->
<!--            <minIndex>1</minIndex>-->
<!--            <maxIndex>3</maxIndex>-->
<!--        </rollingPolicy>-->
<!--        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">-->
<!--            <fileNamePattern>-->
<!--                ../logs/CTRL_log_%d{dd-MM-yyyy}.log-->
<!--            </fileNamePattern>-->
<!--            <maxHistory>10</maxHistory>-->
<!--            <totalSizeCap>100MB</totalSizeCap>-->
<!--        </rollingPolicy>-->
        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
            <fileNamePattern>../logs/CTRL_log-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
            <maxHistory>20</maxHistory>
            <maxFileSize>10MB</maxFileSize>
            <totalSizeCap>200MB</totalSizeCap>
        </rollingPolicy>
        <append>true</append>
        <encoder>
            <pattern>
                %d{dd-MM-yyyy HH:mm:ss.SSS} %-5level--- [%thread] %logger{36}.%M  : %msg%n
            </pattern>
        </encoder>
    </appender>


    <!--    PATTERNS    -->
    <!--    %d - outputs the time which the log message occurred in formats that SimpleDateFormat allows.-->
    <!--    %thread - outputs the name of the thread that the log message occurred in.-->
    <!--    $-5level - outputs the logging level of the log message.-->
    <!--    %logger{36} - outputs the package + class name the log message occurred in. The number inside the brackets represents the maximum length of the package + class name. If the output is longer than the specified length it will take a substring of the first character of each individual package starting from the root package until the output is below the maximum length. The class name will never be reduced. A nice diagram of this can be found in the Conversion word docs.-->
    <!--    %M - outputs the name of the method that the log message occurred in (apparently this is quite slow to use and not recommended unless your not worried about performance or the method name is particularly important to you).-->
    <!--    %msg - outputs the actual log message.-->
    <!--    %n - line break-->
    <!--    %magenta() - sets the colour of the output contained in the brackets to magenta (other colours are available).-->
    <!--    highlight() - sets the colour of the output contained in the brackets to the depending on the logging level (for example ERROR = red).-->

    <!--ELK-Stack syslogger-->
    <!--    <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender">-->
    <!--        <syslogHost>127.0.0.1</syslogHost>-->
    <!--        <port>25826</port>-->
    <!--        <facility>LOCAL1</facility>-->
    <!--        <suffixPattern>[%thread] %logger %msg</suffixPattern>-->
    <!--    </appender>-->

    <!--    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">-->
    <!--        <encoder>-->
    <!--            <pattern>%-5relative %-5level %logger{35} - %msg%n</pattern>-->
    <!--        </encoder>-->
    <!--    </appender>-->

    <logger name="org.springframework" level="INFO"/>
    <logger name="jdbc" level="DEBUG" />
    <logger name="jdbc.sqlonly" level="DEBUG" additivity="false">
        <appender-ref ref="FILE"/>
    </logger>

    <root level="DEBUG">
        <!--        <appender-ref ref="STDOUT" /> &lt;!&ndash; Every log will apear on screen log &ndash;&gt;-->
        <appender-ref ref="FILE" />   <!-- Every log will apear on file -->
    </root>
    <include resource="org/springframework/boot/logging/logback/base.xml"/>
</configuration>