Logging Template
Use this template to configure local and remote logging parameters.
Each requires that you specify the minimum severity level of event to log.
Set up local logging in theLog Configurationsection.
Set up remote logging by using theLog Facilities ConfigurationandRemote Log Receiverssections.
Minimum Severity Levels
In decreasing order of severity, the levels are as follows.
| 严重级别 | Description |
|---|---|
| EMERGENCY | 系统是unusable. |
| ALERT | Includes all alarms the appliance generates:CRITICAL,MAJOR,MINOR, andWARNING. |
| CRITICAL | Critical event. |
| ERROR | An error. This is a non-urgent failure. |
| WARNING | A warning condition. Indicates an error will occur if action is not taken. |
| NOTICE | A normal, but significant, condition. No immediate action required. |
| INFORMATIONAL | Informational. Used by Silver Peak for debugging. |
| DEBUG | Used by Support for debugging. |
| NONE | If you selectNONE, no events are logged. |
The bolded part of the name is what displays in the log files.
If you selectNOTICE(the default), the log records any event with a severity of NOTICE, WARNING, ERROR, CRITICAL, ALERT, and EMERGENCY.
These are purely related to event logging levels,notalarm severities, even though some naming conventions overlap. Events and alarms have different sources. Alarms, after they clear, list as the ALERT level in theEvent Log.
Configure Remote Logging
You can configure the appliance to forward all events, at and above a specified severity, to a remote syslog server.
A syslog server is independently configured for the minimum severity level that it will accept. Without reconfiguring, it might not accept as low a severity level as you are forwarding to it.
In theLog Facilities Configurationsection, assign each message/event type (System / Audit / Flow) to a syslog facility level (local0tolocal7).
For each remote syslog server that you add to receive the events, specify the receiver’s IP address, along with the messages’ minimum severity level and facility level.