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.
1.3. Severity levels
Chapter 1. Introduction
35
Summary of Contents for DFL-210 - NetDefend - Security Appliance
Page 25: ...List of Tables 1 Abbreviations 28 25...
Page 26: ...List of Examples 1 Log Message Parameters 27 2 Conditional Log Message Parameters 27 26...
Page 36: ...1 3 Severity levels Chapter 1 Introduction 36...
Page 195: ...2 12 6 route_removed ID 01100006 Chapter 2 Log Message Reference 195...
Page 409: ...2 40 19 scp_failed_not_admin ID 04704000 Chapter 2 Log Message Reference 409...
Page 476: ...2 49 14 zd_block ID 03800014 Chapter 2 Log Message Reference 476...