1.3. Severity levels
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.
Priority in Syslog Messages
In Syslog messages the priority is indicated by the parameter prio=nn.
Excluding Logged Messages
NetDefendOS 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
by NetDefendOS. These features are documented further in the NetDefendOS Administrators
Guide.
Chapter 1: Introduction
43
Summary of Contents for NetDefend DFL-260E
Page 32: ...List of Tables 1 Abbreviations 35 32...
Page 33: ...List of Examples 1 Log Message Parameters 34 2 Conditional Log Message Parameters 34 33...
Page 42: ...routemetric Route metric cost Chapter 1 Introduction 42...
Page 44: ...Chapter 1 Introduction 44...
Page 216: ...Rule Information Connection Chapter 2 Log Message Reference 216...
Page 243: ...client_ip Context Parameters Rule Name Packet Buffer Chapter 2 Log Message Reference 243...
Page 556: ...logger Chapter 2 Log Message Reference 556...
Page 613: ...Parameters location Chapter 2 Log Message Reference 613...
