Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi

Page de 402
 
15-23
AsyncOS 8.3 for Cisco Content Security Management User Guide
 
Chapter 15      Logging
  Log Subscriptions
Note
You can specify different logging levels for each log type.
Creating a Log Subscription in the GUI
Procedure 
Step 1
On the Management Appliance > System Administration > Log Subscriptions page, click Add Log 
Subscription
Step 2
Select a log type and enter the log name (for the log directory), as well as the name for the log file itself.
Step 3
If applicable, specify the maximum file size. 
Step 4
If applicable, specify days, times of day, or time intervals to roll over the logs. For more information, 
see 
Step 5
If applicable, specify the log level. 
Step 6
(Configuration history logs only) Select whether to include passwords in the log.
Note
You cannot load configurations containing masked passwords. If you anticipate loading 
configurations from the configuration history logs, select Yes to include passwords in the log.
Step 7
Configure the log retrieval method.
Step 8
Submit and commit your changes.
Table 15-22
Log Levels 
Log Level
Description
Critical
Only errors are logged. This is the most abbreviated log-level setting. At this log level, 
you cannot monitor performance and important appliance activities; however, the log 
files do not reach maximum size as quickly as they do at a detailed log level. This log 
level is analogous to the syslog level Alert.
Warning
All system errors and warnings are logged. At this log level, you cannot monitor 
performance and important appliance activities. The log files reach maximum size more 
quickly than they do at the Critical log level. This log level is analogous to the syslog 
level Warning.
Information
Second-by-second operations of the system are logged. For example, connections 
opened and delivery attempts are logged. The Information level is the recommended 
setting for logs. This log level is analogous to the syslog level Info.
Debug
More detailed information is logged than at the Information log level. Use the Debug 
log level when you are troubleshooting an error. Use this setting temporarily, and then 
return to the default level. This log level is analogous to the syslog level Debug.
Trace
All available information is logged. The Trace log level is recommended only for 
developers. Using this level causes a serious degradation of system performance and is 
not recommended. This log level is analogous to the syslog level Debug.