Log levels
Levels control which events are processed by Java logging. WebSphere Application Server controls the levels of all loggers in the system.
This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
The level value is set from configuration data when the logger is created and can be changed at run time from the 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. We 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 console, the change is propagated to the children of the logger.
Levels are cumulative; a logger can process logged objects at the level set for the logger, and at all levels above the set level.
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 needed to debug problems All All events are logged. If we create custom levels, All includes the custom levels, and can provide a more detailed trace than Finest. For instructions on how to set logging levels, read the topic about configuring Java logging using the console.
Trace information, which includes events at the Fine, Finer and Finest levels, can be written only to the trace log. If we do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not effect the logged data.
Related concepts
Loggers Log handlers Log filters Log formatters
Related tasks
Configure Java logging using the administrative console
Log level settings