EnGenius EWS Series User Manual page 52

Severity Level
RFC 5424 defines eight severity levels:
Code Severity
0 EMERG
1 ALERT
2 CRIT
3 ERROR
4 WARNING
5 NOTICE
6 INFO
Remote Logging
The internal log of the EWS Switch has a fixed capacity; at a certain level, the EWS Switch will start
deleting the oldest entries to make room for the newest. If you want a permanent record of all logging
activities, you can set up your syslog server to receive log contents from the EWS Switch. Use this page
to direct all logging to the syslog server. Click the Add button, define your syslog server, and select the
severity level of events you wish to log.
Description
System is unusable.
Action must be taken
immediately.
Critical conditions.
Error conditions.
Warning conditions.
Normal but significant
condition.
Informational messages.
General Description
A "panic" condition usually affecting multiple
apps/servers/sites. At this level it would usually
notify all tech staff on call.
Should be corrected immediately, therefore notify
staff who can fix the problem. An example would be
the loss of a primary ISP connection.
Should be corrected immediately, but indicates
failure in a secondary system, an example is a loss of
a backup ISP connection.
Non-urgent failures, these should be relayed to
developers or admins; each item must be resolved
within a given time.
Warning messages, not an error, but indication that
an error will occur if action is not taken, e.g. file
system 85% full - each item must be resolved within
a given time.
Events that are unusual but not error conditions -
might be summarized in an email to developers or
admins to spot potential problems - no immediate
action required.
Normal operational messages - may be harvested for
reporting, measuring throughput, etc. - no action
required.
52