Log level settings


 

+

Search Tips   |   Advanced Search

 

Log levels control which events are processed by Java logging. When you change the level for a logger, the change is propagated to the children of the logger.


Change Log Detail Levels

Enter a log detail level that specifies the components, packages, or groups to trace. The log detail level string must conform to the specific grammar described in this topic. We can enter the log detail level string directly, or generate it using the graphical trace interface.

If we select the Configuration tab, a static list of well-known components, packages, and groups is displayed. This list might not be exhaustive.

If we select the Runtime tab, the list of components, packages, and group are displayed with all the components that are registered on the running appserver and in the static list.

The format of the log detail level specification is:

<component> = <level>

...where <component> is the component for which to set a log detail level, and <level> is one of the valid logger levels...

Separate multiple log detail level specifications with colons (:). Components correspond to Java packages and classes, or to collections of Java packages. Use an asterisk (*) as a wildcard to indicate components that include all the classes in all the packages that are contained by the specified component. For example:

* Specifies all traceable code running in the appserver, including WAS system code and customer code.
com.ibm.ws.* Specifies all classes with the package name beginning with com.ibm.ws.
com.ibm.ws.classloader.JarClassLoader JarClassLoader class only.

An error can occur when setting a log detail level specification from the admin console if selections are made from both the Groups and Components lists. In some cases, the selection made from one list is lost when adding a selection from the other list. To work around this problem, enter the log detail level spec directly into the log detail level entry field.

Select a component or group to set a log detail level. The table following lists the valid levels for appservers at WAS V 6 and later, and the valid logging and trace levels for earlier versions:


Table 1. Valid logging levels

Version 6 logging level Logging level before V6 Trace level before V6 Content / Significance
Off Off All disabled* Logging is turned off.

* In V6, a trace level of All disabled turns off trace, but does not turn off logging. Logging is enabled from the Info level.

Fatal Fatal - Task cannot continue and component, application, and server cannot function.
Severe Error - Task cannot continue but component, application, and server can still function. This level can also indicate an impending fatal error.
Warning Warning - Potential error or impending error. This level can also indicate a progressive failure (for example, the potential leaking of resources).
Audit Audit - Significant event affecting server state or resources
Info Info - General information outlining overall task progress
Config - - Configuration change or status
Detail - - General information detailing subtask progress
Fine - Event Trace information - General trace + method entry, exit, and return values
Finer - Entry/Exit Trace information - Detailed trace
Finest - Debug Trace information - A more detailed trace that includes all the detail that is needed to debug problems
All   All enabled All events are logged. If we create custom levels, All includes those levels, and can provide a more detailed trace than finest.

When you enable a logging level in V6.0 or above, we are also enabling all of the levels with higher severity. For example, if we set the logging level to warning on the V6.x application server, then warning, severe and fatal events are processed.

Trace information, which are events at the Fine, Finer and Finest levels, can be written only to the trace log. Therefore, if we do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest will not have an effect on the data that is logged.


 

Related tasks


Set Java logging

 

Related


Tracing and logging configuration