Logging Settings Local Cluster Configuration
Polycom, Inc. 81
The following table describes the fields on the Logging Settings page.
See also:
“Local Cluster Configuration” on page 63
“Local Cluster Configuration Procedures” on page82
Table 4-10 Fields on the Logging Settings page
Field Description
Logging level Leave the default, Production, unless advised to
change it by Polycom support. Debug is useful for
troubleshooting. Verbose debug is not recommended
for production systems.
Rolling frequency If rolling the logs daily (the default) produces logs that
are too large, shorten the interval.
Retention period The number of days to keep log archives. For most
systems, we recommend setting this to 7.
Alert when logs exceed The percentage of the 1 GB log file capacity in use at
which the system displays a warning on the dashboard.
Local log forwarding Enables you to forward selected log entries to a central
log management server (such as Graylog2).
Specify:
•The address of the destination server. It must be
running some version of syslog.
•The socket type (transport) for which the destination
server’s version of syslog is configured. Most
versions of syslog support only UDP, the default, but
syslog-ng also supports TCP.
•The facility value. Default is Local0.
•The log or logs to forward.
Note: The DMA system’s server.log entries are mapped
to syslog-compliant severities (a “warn” message from
server.log arrives at the destination server. with
syslog-compliant “warn” level). All other logs being
forwarded are assigned the syslog-compliant “notice”
severity.
Each log message is forwarded with its server-side
timestamp intact. The receiving syslog adds its own
timestamp, but preserving the DMA-applied timestamp
makes it easier to accurately troubleshoot time-sensitive
events.