Developer Partner Community

Setting Log Levels for Diagnostic Logging in WebLogic 12.2 by Lucas Jellema

Juergen Kress
PaaS Partner Adoption



Applications and framework libraries running on WebLogic produce logging at various levels: error, warning, information, debug (fine and finer). WebLogic allows us to specify what level of logging should be written to the log files. Under normal circumstances administrators will probably require no more than error or perhaps warning level. In times of problematic behavior when more detailed analysis is required, we may want to switch to finer grained logging output.

It is possible to not only define the logging levels at runtime but to also define the current production log level per logger (corresponding to a package or class)- and have settings inherited to lower levels in the package hierarchy.

This article very briefly shows how to set the logging levels in WebLogic 12c Release 2 – where the interface is just a little different from previous releases. Note: the underlying objective of this article is to prepare logging that will be processed by Oracle Management Cloud – Log Analytics.

Open the Enterprise Manager Fusion Middleware Control console.

The logging levels are not configured at domain level:

But at (managed) server level. Drill down to the relevant server, amispaas_server1 in this example. Open the dropdown menu at the top, click on Logs and select Log Configuration from the submenu: Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic,WebLogic Community,Oracle,OPN,Jürgen Kress

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.