Logging configuration

Technical Library | Support

Go to the table of contents

Go to the previous page

Go to the next page

View or print as PDF

Configuration Files > records.config > Logging configuration

Logging configuration

Help | Content Gateway | Version 7.8.x

Configuration Variable

proxy.config.log2.
logging_enabled

Enables and disables event logging:

0 = logging disabled

1 = log errors only

2 = log transactions only

3 = full logging (errors + transactions)

See Working With Log Files.

proxy.config.log2.
max_secs_per_buffer

Specifies the maximum amount of time before data in the buffer is flushed to disk.

proxy.config.log2.
max_space_mb_for_logs

5120 or 20480

Specifies the amount of space allocated to the logging directory, in megabytes.

When Content Gateway is on a V-series appliance, the size is 5120 (5 GB) and cannot be changed.

When Content Gateway is installed on a stand-alone server, the default size is 20480 (20 GB) and the size is configurable.

proxy.config.log2.
max_space_mb_for_orphan_logs

Specifies the amount of space allocated to the logging directory, in megabytes, if this node is acting as a collation client.

proxy.config.log2.
max_space_mb_headroom

Specifies the tolerance for the log space limit in bytes. If the variable proxy.config.log2.
auto_delete_rolled_file is set to 1 (enabled), auto-deletion of log files is triggered when the amount of free space available in the logging directory is less than the value specified here.

proxy.config.log2.
hostname

Specifies the hostname of the machine running Content Gateway.

proxy.config.log2.
logfile_dir

Specifies the full path to the logging directory.

proxy.config.log2.
logfile_perm

Specifies the log file permissions. The standard UNIX file permissions are used (owner, group, other). Valid values are:

- = no permission

r = read permission

w = write permission

x = execute permission

Permissions are subject to the umask settings for the Content Gateway process. This means that a umask setting of 002 will not allow write permission for others, even if specified in the configuration file.

Permissions for existing log files are not changed when the configuration is changed.

proxy.config.log2.
custom_logs_enabled

When enabled (1), supports the definition and generation of custom log files according to the specifications in logs_xml.config.

See logs_xml.config.

proxy.config.log2.
xml_logs_config

Specifies the size, in MB, which when reached causes the log files to roll. See Rolling event log files.

proxy.config.log2.
squid_log_enabled

Enables (1) or disables (0) the squid log file format.

proxy.config.log2.
squid_log_is_ascii

Specifies the squid log file type:

proxy.config.log2.
squid_log_name

Specifies the squid log filename.

proxy.config.log2.
squid_log_header

Specifies the squid log file header text.

proxy.config.log2.
common_log_enabled

Enables (1) or disables (0) the Netscape common log file format.

proxy.config.log2.
common_log_is_ascii

Specifies the Netscape common log file type:

proxy.config.log2.
common_log_name

Specifies the Netscape common log filename.

proxy.config.log2.
common_log_header

Specifies the Netscape common log file header text.

proxy.config.log2.
extended_log_enabled

Enables (1) or disables (0) the Netscape extended log file format.

proxy.confg.log2.
extended_log_is_ascii

Specifies the Netscape extended log file type:

proxy.config.log2.
extended_log_name

Specifies the Netscape extended log filename.

proxy.config.log2.
extended_log_header

Specifies the Netscape extended log file header text.

proxy.config.log2.
extended2_log_enabled

Enables (1) or disables (0) the Netscape Extended-2 log file format.

proxy.config.log2.
extended2_log_is_ascii

Specifies the Netscape Extended-2 log file type:

proxy.config.log2.
extended2_log_name

Specifies the Netscape Extended-2 log filename.

proxy.config.log2.
extended2_log_header

Specifies the Netscape Extended-2 log file header text.

proxy.config.log2.
separate_host_logs

When enabled (1), configures Content Gateway to create a separate log file for HTTP/FTP transactions for each origin server listed in the log_hosts.config file (see HTTP host log splitting).

proxy.local.log2.
collation_mode

Specifies the log collation mode:

0 = Collation disabled.

1 = This host is a log collation server.

2 = This host is a collation client and sends entries using standard formats to the collation server.

For information on sending XML-based custom formats to the collation server, see logs_xml.config.

proxy.confg.log2.
collation_host

Specifies the hostname of the log collation server.

proxy.config.log2.
collation_port

Specifies the port used for communication between the collation server and client.

proxy.config.log2.
collation_secret

Specifies the password used to validate logging data and prevent the exchange of unauthorized information when a collation server is being used.

proxy.config.log2.
collation_host_tagged

When enabled (1), configures Content Gateway to include the hostname of the collation client that generated the log entry in each entry.

proxy.config.log2.
collation_retry_sec

Specifies the number of seconds between collation server connection retries.

proxy.config.log2.
rolling_enabled

Enables (1) or disables (0) log file rolling.

See Rolling event log files.

proxy.config.log2.
rolling_interval_sec

Specifies the log file rolling interval, in seconds. The minimum value is 300 (5 minutes). The maximum value is 86400 seconds (one day).

proxy.config.log2.
rolling_offset_hr

Specifies the file rolling offset hour. The hour of the day that starts the log rolling period.

proxy.config.log2.
rolling_size_mb

Specifies the size, in megabytes, which when reached causes the current file to be closed and a new file to be created.

proxy.config.log2.
auto_delete_rolled_files

Enables (1) or disables (0) automatic deletion of rolled files.

proxy.config.log2.
sampling_frequency

Configures Content Gateway to log only a sample of transactions rather than every transaction. You can specify the following values:

1 = log every transaction

2 = log every second transaction

3 = log every third transaction

Go to the table of contents

Go to the previous page

Go to the next page

View or print as PDF

Configuration Files > records.config > Logging configuration

Copyright 2016 Forcepoint LLC. All rights reserved.