Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip
titleAbiquo Log Documentation

The Abiquo Logs are described in detail the Troubleshooting section of this wiki.

Log Files 

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

...

The logback config file is in WEB-INF/classes in each webapp directory and can be edited. 

 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 is shown here. Note that some of the loggers are set to a log level of TRACE. This log level can create large logs. A log level of DEBUG should be sufficient for both the VSM and BPM.

Code Block
<?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>

 

Log Rotation Example

The following example shows the default logback rollingPolicy configuration for nodecollector 

...

Code Block
titlelogback.xml
<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>

 

Disk Requirements

This section describes how to calculate the disk space requirements for the webapp logs. Customers must determine their own logging requirements.Abiquo recommends that you keep approximately one months' worth of files

If you set 30 days (expected) as retention time for webapps' logs, the worst-case scenario for disk space is:
Monolithic
7 webapps * 50 MB max file size * 30 rotations by day or size = 10.5 GB 
Catalina, rotates weekly or when size > 100 MB, 10 rotations keept = 1 GB
This space should be reserved on /opt/abiquo/tomcat/logs. Abiquo recommends that customers should create a isolated logicalvolume of approximately 15 GB and mount it on the /opt/abiquo/tomcat/logs path.