D4Science Infrastructure

Also, add the following configuration on the dataminers (the log path will change):

<appender name="ANALYSIS"
                class="ch.qos.logback.core.rolling.RollingFileAppender">
                <file>/home/gcube/SmartGears/analysis.log</file>
                <append>true</append>
                <encoder>
                        <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{0}: %msg%n
                        </pattern>
                </encoder>
                <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
                        <fileNamePattern>/home/gcube/SmartGears/analysis.%d{yyyy-MM-dd}.log
                        </fileNamePattern>
                        <maxHistory>30</maxHistory>
                </rollingPolicy>
        </appender>

       <logger name="org.gcube.dataanalysis" level="DEBUG">
                <appender-ref ref="ANALYSIS" />
        </logger>

Another parameter that can be configured is maxHistory: 30 days is usually too much.

Last: if a size based rolling appender can be configured, this would be very helpful to keep the total log size under control.

Since logback 1.1.7 there's an appender called SizeAndTimeBasedRollingPolicy that does exactly what I'm asking. A reference: https://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedRollingPolicy

@lucio.lelii@isti.cnr.it smartgear comes with logback 1.0.13 and it's too old to support the new rolling appender. We should upgrade to at least 1.1.7

Lucio Lelii wrote:

The appender configuration is not correct for this new version, you have to add the %i suffix to the fileNamePattern:

<fileNamePattern>/home/gcube/SmartGears/analysis.%d{yyyy-MM-dd}.%i.log

Done.