Syslog severity table
PS The lower the code, the more serious the message!
||System is unusable.
||A “panic” condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
||Action must be taken immediately.
||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.
||Normal but significant condition.
||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.
||Info useful to developers for debugging the application, not useful during operations.