Appendix A: Severity Levels
Main Severity Levels
The following are the different levels of severity and their relevant values, in ascending order :
Severity |
Value |
Details |
DEBUG |
100 |
For debugging purposes, with extensive and low level information. |
PATH |
200 |
For tracing the execution flow. For example, it is used in the context of entering and leaving a method, looping and branching operations. |
INFO |
300 |
Informational text, mostly for echoing what has been performed. |
WARNING |
400 |
Announces that the application can recover from an anomaly and fulfill the required task, but needs attention from developer/operator. |
ERROR |
500 |
Announces that the application can recover from error, but cannot fulfill the required task due to the error. |
FATAL |
600 |
Announces that the application cannot recover from error, and 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 such a severity are logged only by controllers with the same severity. All other controllers suppress those messages. |
NONE |
701 |
The highest severity. Log controllers with such a severity logged only the messages with severity NONE. Messages with that severity are logged by all the log controllers, regardless of their severity. |
The class Severity.java is part of the SAP Logging API. You can find detailed information about severities in com.sap.tc.logging.