Limit the Number of Audit Log Files Kept by Integration Server

By default, Integration Server keeps audit log files for file-based audit loggers indefinitely. Because audit log files can rapidly become large or numerous when using more verbose logging levels or under heavy loads, you might want to limit the number audit log files that Integration Server keeps for each logger on the file system. Limiting the number of files is sometimes referred to as pruning.

Integration Server provides the watt.server.audit.logFilesToKeep server configuration parameter for limiting the number of audit log files that Integration Server maintains on the file system for each logger, including the current log file for the logger. When the number of log files for an audit logger reaches the established limit, Integration Server deletes the oldest audit log file each time Integration Server rotates the audit log for the logger at midnight or due to size limitations. Integration Server also prunes the number of audit log files for an audit logger when creating a new log file for the audit logger. For example, after Integration Server start up, the audit logger writes log data to a new file. If, after creating the new audit log file, Integration Server determines the number of log files for the logger exceeds the maximum allowed, Integration Server deletes the oldest audit log file.

Following are some examples of values for watt.server.audit.logfilesToKeep and the resulting Integration Serverbehavior:

If you set watt.server.audit.logFilesToKeep to n, Integration Server keeps the current audit log file for a logger and up to n-1 archived audit log files. For example, if you set watt.server.audit.logFilesToKeep to 30 and the session logger is configured to write to a file, Integration Server keeps the current session log file and up to 29 archived session log files.

If you set watt.server.audit.logFilesToKeep to 1, Integration Server keeps the current audit log file for a logger and no previous audit log files. When Integration Server rotates the audit log for a logger that writes to a file, Integration Server does not keep the previous audit log for the logger

If you set watt.server.serverlogFilesToKeep to 0, or any value less than 1, Integration Server keeps an unlimited number of audit log files for each audit logger that writes to a file

The default value of watt.server.audit.logFilesToKeep is 0, indicating that there is no limit to the number of audit log files that Integration Server maintains for an audit logger that write to file.

The watt.server.audit.logFilesToKeep parameter affects only the audit loggers configured to write to a file with the exception of the FailedAudit logs. The parameter does not affect audit loggers configured to write to a database.