Appendix A: Severity Levels

Use

Main Severity Levels

Severity	Value	Details
DEBUG	100	For debugging purposes, with extensive and low level information.
PATH	200	For tracing the execution flow. It is used, for example, in the context of entering and leaving a method, looping and branching operations.
INFO	300	Informational text, mostly for echoing what is performed.
WARNING	400	Announces that the application can recover from an anomaly and fulfill the required task. However, it needs attention from developer/operator.
ERROR	500	Announces that the application can recover from error. However, it cannot fulfill the required task due to the error.
FATAL	600	Announces that the application cannot recover from error. The severe situation causes a fatal termination.

Extra Severity Levels

Severity	Value	Details
ALL	0	The lowest severity. Controller with such a severity logs all the messages, regardless of their severity. Messages with severity ALL are logged only by controllers with the same severity. All other controllers suppress those messages.
NONE	701	The highest severity. Log controllers with severity NONE logged only the messages with the same severity. Messages with that severity are logged by all the log controllers, regardless of their severity.

Severity

Value

Details

ALL

The lowest severity.

Controller with such a severity logs all the messages, regardless of their severity.

Messages with severity ALL are logged only by controllers with the same severity. All other controllers suppress those messages.

NONE

701

The highest severity.

Log controllers with severity NONE logged only the messages with the same severity.

Messages with that severity are logged by all the log controllers, regardless of their severity.

Note

The class Severity.java is part of the SAP Logging API.

You can find detailed information about severities in com.sap.tc.logging .