8-15
Cisco Global Site Selector Administration Guide
OL-10410-01
Chapter 8 Viewing Log Files
Viewing System Logs from the Primary GSSM GUI
•
Module—GSS component that logs the message (for example, server or
storeAdmin).
•
Severity—Severity of the logged message. The GSS rates system log
messages using one of the following four severity levels:
–
Fatal
—
A failure in the GSS or one of its components. Fatal errors are rare
and are usually caused by exceptions from which it is impossible to
recover, or by the failure of a GSS component to initialize properly.
–
Warning—A noncritical error or unexpected condition.
–
Info—Information about the normal operation of the GSS and its
components.
–
Debug—Detailed information about the internal operations of the GSS or
one of its components. Debug log messages are intended for use by Cisco
support engineers to troubleshoot a problem.
•
Description—Text description that explains the event.
•
Message—Information about any relevant conditions encountered while the
event was being logged.
3.
Click the column header of any of the displayed columns (except for Severity
or Description) to sort the listed domains by a particular property.
Purging System Log Messages from the GUI
You may want to remove older system log messages from the primary GSSM GUI.
An excessive number of system log messages can make viewing difficult on the
System Log list page of the Tools navigation tab. To purge system log messages
from the primary GSSM database, use the
gssm database purge-log-records
privileged EXEC command from the primary GSSM CLI.
You can instruct the primary GSSM to purge a quantity of system log messages
from the GSSM database except for the following:
•
Specified number of recently generated messages
•
Most recently generated messages (generated over a specified number of days
before today)
The syntax for the
gssm database purge-log-records
command is as follows:
gssm database purge-log-records
{
count
number_records_to_keep
|
days
number_days_to_keep
}
