Cisco Cisco Content Security Management Appliance M390 Guía Del Usuario
C H A P T E R
15-1
AsyncOS 9.1 for Cisco Content Security Management Appliances User Guide
15
Logging
•
•
•
Logging Overview
Log files record regular operations, as well as exceptions, for activity on the system. Use the logs for
monitoring the Cisco Content Security appliance, troubleshooting, and evaluating system performance.
monitoring the Cisco Content Security appliance, troubleshooting, and evaluating system performance.
Most logs are recorded in plain text (ASCII) format; however, tracking logs are recorded in binary format
for resource efficiency. The ASCII text information is readable in any text editor.
for resource efficiency. The ASCII text information is readable in any text editor.
Logging Versus Reporting
Use logging data to debug message flow, reveal basic day-to-day operational information such as FTP
connection details, HTTP log files, and for compliance archiving.
connection details, HTTP log files, and for compliance archiving.
You can access this logging data directly on the Email Security appliance or send it to any external FTP
server for archival or reading. You can either FTP to the appliance to access the logs or push the plain
text logs to an external server for backup purposes.
server for archival or reading. You can either FTP to the appliance to access the logs or push the plain
text logs to an external server for backup purposes.
To view reporting data, use the Report pages on the appliance GUI. You cannot access the underlying
data in any way, and this data cannot be sent to anything but a Cisco Content Security Management
appliance.
data in any way, and this data cannot be sent to anything but a Cisco Content Security Management
appliance.
Note
The Security Management appliance pulls information for all reporting and tracking with the exception
of spam quarantine data. This data is pushed from the ESA.
of spam quarantine data. This data is pushed from the ESA.