Page Comparison

...

This section describes how to configure the Abiquo logs so that old webapp log files are periodically deleted. This will prevent problems due to lack of hard disk spacewebapp logs to reduce the size of these files and periodically delete old files. Customers must determine their own logging requirements and configure the webapp logs in their environment appropriately.

Log Files 

A current log is created for each webapp in the directory \{catalina.base}/logs/ 

In a standard install, this is /opt/abiquo/tomcat/logs. The logs are named after the webapps and renamed with date information when they are rotated.

In Abiquo 2.4, the logs arethe log files have the format *.log, for example:

am.log
api.log
bpm-async.log
catalina.out
nodecollectornars.log
ssm.log
virtualfactory.log
vsm.log

...

 For example, for the nodecollector * webapp, the default file would be /opt/abiquo/tomcat/webapps/nodecollector/WEB-INF/classes/logback.xml

(*Nodecollector is the name of the webapp for the Discovery Manager Remote Service). 

Log Level Example

The default logback.xml file for the VSM in Abiquo 2.4 is shown here. Note that some of the loggers are set to a log level of TRACE, (in the example below: com.abiquo and akka). This log level can create large logsamounts of log data. A log level of DEBUG should be sufficient for both the VSM and BPMmost Abiquo installations.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
        <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
                <layout class="ch.qos.logback.classic.PatternLayout">
                        <Pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} %X{akkaSource} - %msg%n</Pattern>
                </layout>
                <filter class="ch.qos.logback.classic.filter.ThresholdFilter">
                        <level>DEBUG</level>
                </filter>
        </appender>
        <appender name="FILE"
                class="ch.qos.logback.core.rolling.RollingFileAppender">
                <file>${catalina.base}/logs/vsm.log</file>
                <layout class="ch.qos.logback.classic.PatternLayout">
                        <Pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} %X{akkaSource} - %msg%n</Pattern>
                </layout>
                <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
                        <fileNamePattern>${catalina.base}/logs/vsm-%d{yyyy-MM-dd}.%i.log
                        </fileNamePattern>
                        <timeBasedFileNamingAndTriggeringPolicy
                                class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                                <maxFileSize>50MB</maxFileSize>
                        </timeBasedFileNamingAndTriggeringPolicy>
                </rollingPolicy>
        </appender>
        <logger name="com.abiquo">
                <level value="TRACE" />
        </logger>
        <logger name="akka">
                <level value="TRACE" />
        </logger>
    <logger name="org.jinterop">
        <level value="ERROR" />
    </logger>
        <root>
                <level value="DEBUG" />
                <appender-ref ref="STDOUT" />
                <appender-ref ref="FILE" />
        </root>
</configuration>

...

Set the maxHistory size for each log file by adding a line after maxFileSize and changing the replacing \{NUMBER OF FILES TO KEEP} as shown in the example belowwith a suitable number, for example, 30.

<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
  <fileNamePattern>${catalina.base}/logs/nodecollector-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
  <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
    <maxFileSize>50MB</maxFileSize>
    <maxHistory>{NUMBER OF FILES TO KEEP}</maxHistory>
  </timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy>

To enable automatic log compression, set the filename extension as .gz for each log file. This will compress each log automatically to GZIP format each midnight with the daily rollover. For instance, if you want to compress nodecollector logs you would issue:

  <fileNamePattern>${catalina.base}/logs/nodecollector-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>

Disk Requirements

This section describes how to calculate the disk space requirements for the webapp logs. Customers must determine their own logging requirements.

...

Changes apply within 60 seconds

In versions prior to Abiquo 3.4, after you have made you changes restart the Tomcat server.

In Abiquo 3.4 and later versions, do not restart the Tomcat server because modifications will be applied within 60 seconds.