131
Code Severity Description General Description
0
Emergency System is unusable A emergency condition usu-
ally affecting multiple apps/
servers/sites. Direct Attention
is required.
1
Alert Actions must be
taken immediately
Should be corrected immedi-
ately.Notifystaffwhocanx
the problem promptly.
2
Critical Critical conditions Should be corrected immedi-
ately, but indicates failure in a
secondary system.
3
Error Error conditions Non-urgent failures, these
should be relayed to devel-
opers or admins; each item
should be resolved promptly.
4
Warning Warning conditions Warning message that indi-
cates an error will occur if
action is not taken.
5
Notice Normalbutsigni-
cant conditions
Events that are unusual but
not error inducing. No immedi-
ate action required.
6
Informational Informational
message
Normal operational status
may be gained for reporting
procedures.
7
Debug Debug-level mes-
sages
Information useful to devel-
opers for debugging applica-
tions.
Log
The Syslog Protocol allows devices to send event
noticationmessagesinresponsetoevents,faults,or
errors occurring on the platform as well as changes in
congurationorotheroccurrencesacrossanIPnetwork
to syslog servers. It then collects the event messages,
providing powerful support for users to monitor network
operation and diagnose malfunctions. A Syslog-enabled
device can generate a syslog message and send it to a
Syslog server.
SyslogisdenedinRFC3164.TheRFCdenes
the packet format, content, and system log related
information of Syslog messages. Each Syslog message
has a facility and severity level. The Syslog facility
identiesaleintheSyslogserver.Refertothe
documentation of your Syslog program for details. The
following table describes the Syslog severity levels.
Comments to this Manuals