- Sign into the WebSphere web console.
- In the left panel, expand Troubleshooting and select Logs and Trace.
- Select the component that you want to adjust logging on, such as an application server, node, or deployment manager.
- Select Change log detail levels.
- In the Change log detail levels box, enter a new log level.
By default, the log level is *=info.
*=fine, *=finer, or *=finest can be used to add additional debugging details to the logs. Logging should only be set to finest while diagnosing an issue, and should be return to info after debugging is done, as finest can reduce the performance of the JVM and to also cause the log files to quickly roll.
Checkmarking "Disable logging and tracing of potentially sensitive data" will prevent sensitive information, such as credit card numbers, from being written to logs. There is a tradeoff here. The benefit is that security will be enhanced, as the possibility of sensitive data getting into the wrong hands is decreased. The drawback is that is may be more difficult to diagnose some problem. For example, if users are reporting an issue with credit card sumissions, the diabling of the writing of credit card numbers to the logs will make it more difficult to debug issues with credit card transactions.
- Select Save.
- Restart the JVM.