Logging Message Format

Last published : Nov 13, 2026

Facility

The syslog facility value is an integer from 0-23. See the Syslog protocol definition in RFC 5424 for more information about facility values.

Severity

The severity is an integer from 0-7. The following table describes the severity levels, and how Java log levels are mapped to them:
Syslog Severity Levels
Code Severity Java Level Description General Description
0 Emergency System is unusable. A "panic" condition usually affects multiple apps/servers/sites. At this level it usually notifies all tech staff on call.
1 Alert Action must be taken immediately. Must be corrected immediately, therefore notify staff who can fix the problem. For example, the loss of a primary ISP connection.
2 Critical Critical conditions. Must be corrected immediately, but indicates failure in a secondary system. For example, the loss of a backup ISP connection.
3 Error SEVERE Error conditions. Non-urgent failures, these must be relayed to developers or admins; each item must be resolved within a given time.
4 Warning WARNING Warning conditions. Warning messages, not an error, but indication that an error occurs if action is not taken. For example, file system 85% full - each item must be resolved within a given time.
5 Notice 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.
6 Informational INFO, CONFIG Informational messages. Normal operational messages - might be harvested for reporting, measuring throughput, and so on - no action required.
7 Debug FINE,FINER, FINEST Debug-level messages. Info useful to developers for debugging the application, not useful during operations.