Select Log Transactions and Errors to log transactions into your selected event log files and errors in the error log files.

Select Log Transactions Only to log transactions into your selected event log files only. Content Gateway does not log errors in the error log files.

Select Log Errors Only to log errors in the error log files only. Content Gateway does not log transactions into your selected event log files.

Select Disabled to turn off logging.

Note: Transaction logs can consume a lot of space. Make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.

Specifies the tolerance for the log space limit. If the Auto-Delete Rolled Files option is enabled, autodeletion is triggered when the amount of free space available in the logging directory is less than the headroom.

Enables or disables log file rolling. To keep log files down to manageable sizes, you can roll them at regular intervals. See Rolling event log files.

Specifies the amount of time Content Gateway enters data in log files before rolling them to .old files. The minimum value is 300 seconds (five minutes). The default value is 21600 seconds (6 hours). The maximum value is 86400 (1 day).

Enables autodeletion of rolled log files when available space in the log directory is low. Autodeletion is triggered when the amount of free space available in the log directory is less than the Log Space Headroom.

Caution: To achieve the expected results and avoid unexpected network behaviors, before enabling this option be sure that reverse DNS is configured in your network.

Select ASCII or Binary as the type of log files to be created.

Specifies the name used for Squid log files. The default filename is squid.log.

Select ASCII or Binary as the type of log file to be created.

Specifies the name used for Netscape Common log files. The default filename is common.log.

Select ASCII or Binary as the type of log file to be created.

Specifies the name used for Netscape Extended log files. The default filename is extended.log.

Select ASCII or Binary as the type of log file to be created.

Specifies the name used for Netscape Extended-2 log files. The default filename is extended2.log.

Specifies the log collation mode for this Content Gateway node. You can use the log file collation feature to keep all logged information in one place. For more information about log file collation, see Collating event log files.

Select Collation Disabled to disable log collation on this Content Gateway node.

Select Be a Collation Server to configure this Content Gateway node to be the collation server.

Select Be a Collation Client to configure this Content Gateway server to be a collation client. A Content Gateway server configured as a collation client sends only the active standard log files, such as Squid, Netscape Common, and so on, to the collation server. If you select this option, enter the hostname of the collation server for your cluster in the Log Collation Server field.

Note: When logs are collated, the source of the log entry—its node of origin—is lost unless you turn on the Log collation host tagged option (described below).

If you want Content Gateway as a collation client to send custom (XML-based) log files, you must specify a LogObject in the logs_xml.config file.

Displays the logs_xml.config file so that you can configure custom (XML-based) logging options.