Administer > Monitor your network > Monitor Syslog messages > Syslog severities

Syslog severities

The following table provides a list of Syslog severity levels with descriptions and suggested actions for each.

Number

Severity

Suggested Actions

0

Emergency

A "panic" condition affecting multiple applications, servers, or sites. System is unusable. Notify all technical staff on call.

1

Alert

A condition requiring immediate correction, for example, the loss of a backup ISP connection. Notify staff who can fix the problem.

2

Critical

A condition requiring immediate correction or indicating a failure in a primary system, for example, a loss of a primary ISP connection. Fix CRITICAL issues before ALERT-level problems.

3

Error

Non-urgent failures. Notify developers or administrators as errors must be resolved within a given time.

4

Warning

Warning messages are not errors, but they indicate that an error will occur if required action is not taken. An example is a file system that is 85% full. Each item must be resolved within a given time.

5

Notice

Events that are unusual but are not error conditions. These items might be summarized in an email to developers or administrators to spot potential problems. No immediate action is required.

6

Informational

Normal operational messages. These may be harvested for network maintenance functions like reporting and throughput measurement. No action is required.

7

Debug

Information useful to developers for debugging an application. This information is not useful during operations.