Network Deployment (Distributed operating systems), v8.0 > Reference > Log and trace file descriptions
Log level settings
Use this topic to configure and manage log level settings.
Use 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.
New feature: Beginning in WAS v8.0 you 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 or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:
Disable logging and tracing of potentially sensitive data
The application server has a list of loggers which are known to potentially write sensitive information to the log and trace when enabled. For example, enabling certain HTTP related loggers at FINEST level may result in confidential user-specified information from HTTP requests being stored in the trace files. If you want the server to avoid enabling these loggers at levels which are known to be used for potentially sensitive information, check the "Disable logging and tracing of potentially sensitive data" checkbox. When the server is started, or when the log detail level specification is modified at runtime, the server will compare the list of loggers and levels specified in the log detail level specification to the list of loggers and levels in the sensitive logger list, and will update the log detail level specification as needed.
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 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:
*
Specifies all traceable code running in the application server, including the product 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 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.
Select a component or group to set a log detail level. The table following lists the valid levels for application servers at WAS v6 and later, and the valid logging and trace levels for earlier versions. Logging level values are case-sensitive and begin with a lower-case letter.
When you enable a logging level in v6.0 or above, you are also enabling all of the levels with higher severity. For example, if you set the logging level to warning on your Version 6.x application server, then warning, severe and fatal events are processed.
Valid logging levels. The following table lists the valid levels for application servers at WAS Version 6 and later, and the valid logging and trace levels for earlier versions.
Version 6 logging level Log level before v6 Trace level before v6 Content / Significance off off All disabled* Log 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 you create custom levels, All includes those levels, and can provide a more detailed trace than finest. [Basic mode logging] 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.
Configure Java logging
Related
Trace and logging configuration