1.2. Severity levels

Home Prev	cOS Stream 4.00.03 Log Reference Guide	Next

An event has a default severity level, based on how serious the event is. The following eight severity levels are possible, as defined by the Syslog protocol:

0 - Emergency: Emergency conditions, which most likely led to the system being unusable.
1 - Alert: Alert conditions, which affected the functionality of the unit. Needs attention immediately.
2 - Critical: Critical conditions, which affected the functionality of the unit. Action should be taken as soon as possible.
3 - Error: Error conditions, which probably affected the functionality of the unit.
4 - Warning: Warning conditions, which could affect the functionality of the unit.
5 - Notice: Normal, but significant, conditions.
6 - Informational: Informational conditions.
7 - Debug: Debug level events.

The Dynamic Severity

There is an additional severity type called Dynamic which does not fit into the progressive severity list given above. A severity of Dynamic means that the severity of the log event can change. There are two uses for this severity type:

The system can set the severity of the event to a specific level to indicate that the triggering condition has not been dealt with.
The severity of the event can be explicitly set by the administrator.

Priority in Syslog Messages

In Syslog messages the priority is indicated by the parameter prio=nn.

Excluding Logged Messages

The Clavister cOS Stream allows the exclusion from logging of entire catageories of log messages or just specific log messages. It is also possible to change the severity level of log messages so that a specific category or a specific message has the severity reset to a particular level when it is sent. These features are documented further in the separate Clavister cOS Stream Administrators Guide.