Use this topic to configure and manage log level settings.
Using log levels you can 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.
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. You can enter the log detail level string directly, or generate it using the graphical trace interface.
If you select the Configuration tab, a static 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 group are displayed with all the components that are registered on the running application server 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 (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 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:
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 log detail level specification directly into the log detail level entry field.
| Version 6 logging level | Logging level before Version 6 | Trace level before Version 6 | Content / Significance |
| Off | Off | All disabled* | Logging is turned off.
* In Version 6, 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 you create custom levels, All includes those levels, and can provide a more detailed trace than finest. |
warning on your Version 6.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 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.
Related reference
Tracing and logging configuration
Searchable topic ID: utrb_loglevel