Appendix A 
Severity Levels
The following table lists the different levels of severity in ascending order:
Definition of Severity Levels
Severity |
Value |
Details |
MIN |
0 |
Minimum restriction |
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 |
The application can recover from an anomaly and fulfill the required task, but needs attention from developer/operator |
ERROR |
500 |
The application can recover from error, but cannot fulfill the required task due to the error |
FATAL |
600 |
The application cannot recover from error, and the severe situation causes a fatal termination |
MAX |
700 |
Maximum restriction |
Here are the other two useful severity keywords that enable and disable tracing/logging:
Severity |
Value |
Details |
ALL |
0 |
Output messages of all severity |
NONE |
701 |
No messages will be logged |