Levels control which events are processed by Java™ logging. WebSphere® Application Server controls the levels of all loggers in the system.
The level value is set from configuration data when the logger is created and can be changed at run time from the administrative console. If a level is not set in the configuration data, a level is obtained by proceeding up the hierarchy until a parent with a level value is found. You can also set a level for each handler to indicate which events are published to an output device. When you change the level for a logger in the administrative console, the change is propagated to the children of the logger.
Level | Content / Significance |
---|---|
Off | No events are logged. |
Fatal | Task cannot continue and component cannot function. |
Severe | Task cannot continue, but component can still function |
Warning | Potential error or impending error |
Audit | Significant event affecting server state or resources |
Info | General information outlining overall task progress |
Config | Configuration change or status |
Detail | General information detailing subtask progress |
Fine | Trace information - General trace |
Finer | Trace information - Detailed trace + method entry / exit / return values |
Finest | Trace information - A more detailed trace - Includes all the detail that is needed to debug problems |
All | All events are logged. If you create custom levels, All includes your custom levels, and can provide a more detailed trace than Finest. |