Control size and number of log files

Answer

The netcool.log and netcool-errors.log files are controlled by properties in the file:

$NCHOME/eWAS/properties/log4j.properties

there are the properties:

log4j.appender.NETCOOL.maxBackupIndex=[i]
log4j.appender.NETCOOL.maxFileSize=[n]MB
 
log4j.appender.NETCOOL-ERRORS.maxBackupIndex=[i]
log4j.appender.NETCOOL-ERRORS.maxFileSize=[n]MB

 
where [i] is the number of rollover files (3 by default, plus the current/active file) and [n] is the size threshold at which the files rollover (10(MB) by default).  Editing this file can be performed while Impact is shutdown (ewas.sh/ewasImpactStartStop.sh stop) as alterations require a restart to enable (ewas.sh/ewasImpactStartStop.sh start).

The Service log files are controlled are controlled globally by the size property:

impact.policylogger.maxlogsizebytes=[value]

where [value] is the size threshold at which roll over should occur in bytes and this is set in the file:

$NCHOME/impact/etc/[ImpactServerName]_policylogger.props

and the number of roll over files by the property:

impact.server.logging.maxlogfiles=[n]

where [n] is the number of times the log file should roll over and this is set in the file:

$NCHOME/impact/etc/[ImpactServerName]_server.props

These two properties not exist in the files by default and need to be added to alter the default values 10 files of 10 MB each.

One can override this global number of roll over files individually for each Service with the property:

impact.[ServiceName].maxbackupindex=[n]

where [n] is the number of times the Service log file should roll over and this is set in the individual Service properties file:

$NCHOME/impact/etc/[ImpactServerName]_[ServiceName].props

Again, these properties require an ImpactServer restart to enable.

Further information on these properties is available in the Netcool/Impact Administration Guide.