Log level settings

 

+

Search Tips   |   Advanced Search

 

 

Overview

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

Specifies tracing details.

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 below. We can enter the log detail level string directly, or generate it using the graphical trace interface.

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

If you select the runtime tab, the list of components, packages, and groups is displayed will all such components currently registered on the running server. This list is static; you will not see your application logger names on the runtime tab.

The format of the log detail level specification is...

<component> = <level>

<component> Component for which to set a log detail level
<level> One of the valid logger levels...

  • off
  • fatal
  • severe
  • warning
  • audit
  • info
  • config
  • detail
  • fine
  • finer
  • finest
  • all

Separate multiple log detail level specifications with colons (:).

Components correspond to Java packages and classes, or to collections of Java packages. Use * as a wildcard to indicate components that include all classes in all packages contained by the specified component.

For example:

* All traceable code running in the application server, including WAS system code and customer code.
com.ibm.ws.* All classes whose package name begins with com.ibm.ws.
com.ibm.ws.classloader.JarClassLoader Only the JarClassLoader class.

Note that an error can occur when setting a log detail level specification from the administrative 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 desired log detail level specification directly into the log detail level entry field.

Select a component or group to set a log detail level. The table below lists the valid levels for application servers at WebSphere Application Server V6 and higher, and the valid logging and trace levels for earlier versions:

V6 Logging Level Logging Level pre-V6 Trace Level pre-V6 Significance
Off Off All disabled* Logging is turned off.

In V6, a trace level of "All disabled" will turn off trace, but will not turn off logging. Logging will be enabled from the Info level.

Fatal Fatal - Task cannot continue and component/ application/ server cannot function.
Severe Error - Task cannot continue but component/ application/ 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 / 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 you create custom levels, "All" would include those levels, and could provide a more detailed trace than "finest".
When you enable a logging level in v6, you are also enabling all of the levels above it. For example, if you set the logging level to warning on your v6 application server, then warning, severe and fatal events will be processed.

Note: Trace information, which are events at levels Fine, Finer and Finest, can only be written to the trace log. Therefore, if you 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.