Field

Indicates

Frequency

The rate of recurrence (4 times daily, daily, weekly) at which log files are rotated.

Log File Size

The maximum size of a log file (in Bytes, Kilobytes, Megabytes) on reaching which the log data will be purged to an archive file.

Email

The email address at which you would like to receive logs that are removed from the archive, once the archive threshold is reached.

• Note: If you do not specify an email address, the logs that are being removed from the archive will be deleted instead of being emailed to the address specified.

Number of Archives

The number of log archives that you can retain.

As logs are rotated they are purged into an archive file located in the same directory as the log file. Due to disk space constraints, the number of log archives that you can retain are limited to the number of log archives that you specify. On exceeding this threshold, logs are rotated out of existence, either by emailing them or deleting them.

Compression

A Boolean value indicating whether logs must be compressed before rotating.

When compression is enabled, the existing log file is saved as a compressed targz file and fresh log data written to the existing log file.

For example, if the access-log file for the Apache service has reached the rotate threshold, then it is compressed as an access-log.targz file and fresh logs written to the access-log file, which is now your most current log file.

If compression is disabled, then the existing log data is copied into a new file and fresh log data written to the existing log file.

For example, if the access-log file for the Apache service has reached the rotate threshold, then a new file, access-log.1 is created into which the existing log data is archived, and fresh log data written to the access-log file, which is now your most current log file.