Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Logging
Help | Content Gateway | v8.5.x
Configure > Subsystems > Logging > General
 
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.
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).
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.
Configure > Subsystems > Logging > Formats
 
Select ASCII or Binary as the type of log files to be created.
Select ASCII or Binary as the type of log file to be created.
Select ASCII or Binary as the type of log file to be created.
Select ASCII or Binary as the type of log file to be created.
Configure > Subsystems > Logging > Splitting
 
Configure > Subsystems > Logging > Collation
 
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.
Configure > Subsystems > Logging > Custom
 
Displays the logs_xml.config file so that you can configure custom (XML-based) logging options.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Copyright 2020 Forcepoint. All rights reserved.