141
Appendix B
Traffic Manager Configuration Options
Log space limit (MB)
Specifies the maximum amount of space, in MB, allocated to the logging
directory for the log files.
NOTE:
Transaction logs can consume a lot of space. You should set this limit
high enough to accommodate at least a single day's worth of uncompressed
transaction logs. Also, make sure that this limit is smaller than the actual space
available on the partition that contains the logging directory.
Log space headroom
(MB)
Specifies the tolerance for the log space limit. If autodeletion of old log files is
enabled, autodeletion is triggered when the amount of free space available in the
logging directory is less than the headroom.
Log Collation
Inactive
Disables log collation. If this option is selected, Traffic Server is neither a
collation server nor a collation client.
Be a collation host
Enables Traffic Server to be a log collation host. Since this host will act as the
server, there is no need to enter a value for the to collation host field.
Send standard formats
Enables Traffic Server to be a log collation client. Selecting this option instructs
Traffic Server to send the active standard formats, such as Squid, Netscape
Common, etc., to the log collation server. You must enter the name of this
collation server for your cluster in the to collation host 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).
Log collation consumes cluster bandwidth in sending all log entries to a single
node. It can therefore impact the performance of the cluster.
Send custom non-xml
formats
Enables Traffic Server to be a log collation client. Selecting this option instructs
Traffic Server to send traditional custom formats to the specified host. You must
enter the name of this collation server for your cluster in the to collation host
field.
Traditional custom formats are specified using the
logs.config
file. For more
information, see
Using custom formats‚ on page 103
.
Send standard and
custom non-xml
formats
Enables Traffic Server to be a log collation client. Selecting this option instructs
Traffic Server to send both standard and traditional custom formats to the
specified host. You must enter the name of this collation server for your cluster in
the to collation host field. This option is the same as having the two previous
options enabled at the same time.
Log collation port
Specifies the TCP port identifier that all nodes in the cluster use to exchange
event log entries. You must specify a port number in all cases except when log
collation is inactive. The default port number is 8085.
NOTE:
You should not change the port number unless there is a conflict with
another service already using the port.
Log collation secret
Specifies the password for the log collation server and the other nodes in the
cluster used to validate logging data and prevent the exchange of arbitrary
information.
Log collation host
tagged: yes/no
Select Yes to add the hostname of the Traffic Server node that generated the log
entry to end of the entry in the collated log file.
Log space limit for
orphan log files (MB)
If log collation is enabled, this is the maximum amount of space, in MB,
allocated to the logging directory for storing orphan log files on the Traffic
Server nodes. Orphan log entries are created when it is not possible to contact the
log collation server.
Standard Event Log Formats
Enabled (On/Off)
Turns event logging in the specified format on or off.
Options
Description
