book
Article ID: KB0093574
calendar_today
Updated On:
Description
Description:
Configuring a node's logging to automatically manage the rolling and log size limit.
Symptoms:
The node log file grows to very large size (in GB)
Cause:
NA
Resolution
You will need to edit the logback.xml file. Open and replace the current appender with the following:
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>../log/bwappnode.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>../log/bwappnode%i.log</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>10</maxIndex>
</rollingPolicy>
<triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>10MB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level [%thread] %logger{36} - %msg%n</pattern>
</encoder>
</appender>
You can change the file Index and Size as per your needs
Issue/Introduction
Can bwappnode logging be configured for log file size limit and rolling logs?