Difference between the sladebug.log and slaStatus.log

Products

• iDash Workload Automation

Issue/Introduction

What's the difference between the sladebug.log and slaStatus.log

 

Environment

Release : 12.1

Component : iDASH WORKLOAD AUTOMATION FOR CA 7

Resolution

The difference between the sladebug.log and slaStatus.log.  As you can see below, the slaAppender is a RollingFile Appender and writes the log messages to the sladebug.log file. The corresponding logger is set to log fatal messages from the package (and sub-package) of com.ca.idash.core.sla.

<RollingFile name="slaAppender" fileName="${sys:idash.home}/log/sladebug.log" filePattern="${sys:idash.home}/log/sladebug.${ROLLOVER_FILE_PATTERN}">
            <SizeBasedTriggeringPolicy size="${LOG_FILE_SIZE_100MB}"/>
            <PatternLayout pattern="${LOG_PATTERN}"/>
            <DefaultRolloverStrategy fileIndex="min" max="${ROLLOVER_FILE_MAX}" />
        </RollingFile>

<Logger name="com.ca.idash.core.sla" level="fatal">
            <AppenderRef ref="slaAppender"/>
        </Logger>

Now look at the definition for the slaStatus.log

<RollingFile name="slaStatusAppender" fileName="${sys:idash.home}/log/slaStatus.log" filePattern="${sys:idash.home}/log/slaStatus.${ROLLOVER_FILE_PATTERN}">
            <SizeBasedTriggeringPolicy size="${LOG_FILE_SIZE_20MB}"/>
            <PatternLayout pattern="${LOG_PATTERN}"/>
            <DefaultRolloverStrategy fileIndex="min" max="${ROLLOVER_FILE_MAX_20}" />
        </RollingFile>
<Logger name="com.ca.idash.core.sla.AbstractSLA" level="debug">
            <AppenderRef ref="slaStatusAppender"/>
        </Logger>
        <Logger name="com.ca.idash.core.sla.SESLA" level="debug">
            <AppenderRef ref="slaStatusAppender"/>
        </Logger>
 

Essentially, all debug and higher-level log messages from com.ca.idash.core.sla.AbstractSLA and com.ca.idash.core.sla.SESLA will go into the slaStatus.log file. But, debug messages will come out only for the SLAs included in idash.debug.slas.status in idash.conf file. This is to allow targeted logging to reduce the noise.

If no SLAs are included with the property idash.debug.slas.status, only iNFO and higher level messages will come from the two classes com.ca.idash.core.sla.AbstractSLA and com.ca.idash.core.sla.SESLA.

Since these two classes are also part of the package com.ca.idash.core.sla which is defined with the slaAppender, the same message for these classes will go into both sladebug.log and slaStatus.log.

If the Logger for the slaAppender was set to a lower level than fatal, you would see a difference in messages that go into the two log files sladebug.log and slaStatus.log.

Additional Information