Using Oracle Weblogic Diagnostic Framework

WLDF (WebLogic Diagnostics Framework) is a group of components that work together to collect, archive, and access diagnostic information in real-time.

The following components are part of the WLDF:

  • Diagnostic Image Capture: creates a diagnostic snapshot from the server that can be used for post-failure analysis.
  • Archive: captures and persists data events, log records and metrics from server instances and applications.
  • Instrumentation: adds diagnostic code to WebLogic Server instances and the applications running on them to execute diagnostic actions at specified locations in the code. The Instrumentation component provides the means for associating a diagnostic context with requests so they can be tracked as they flow through the system.
  • Harvester: captures metrics from run-time MBeans, including WebLogic Server MBeans and custom MBeans, which can be archived and later accessed for viewing historical data.
  • Watches and Notifications: provides the means for monitoring server and application states and sending notifications based on criteria set in the watches.
  • Logging services: manage logs for monitoring server, subsystem, and application events.

 

 

 

 

 

 In this section we will introduce you how to use the Administration console to achieve diagnostic information about your servers; if you need further information about WLDF we suggest you having a look through the Oracle documentation: (http://docs.oracle.com/cd/E24329_01/web.1211/e24426/intro.htm)

Creating a new Oracle Weblogic Diagnostic Module

In order to create a new Diagnostic module, perform the following steps:

1.       Expand the “Diagnostics” option from the Domain Structure. From there, select the “Diagnostic modules” and click on “New”.

2.       In the next screen, choose a name and a description for your module: in this example we will show how to create a diagnostic module for collecting information about JVM Heap:

oracle weblogic book oracle weblogic books

Now click on “OK”. You will return to the Summary page.

Our Diagnostic module has been created; however, it still has no metric associated. Click on the Heap Diagnostic module and select the Configuration tab and Collected Metrics sub tab:

oracle weblogic book oracle weblogic books

Click on “New” in order to create a new metric. In the next screen, you need to choose between “Server runtime” and “Domain runtime” metrics. (The former means that metrics will be collected at server level; the other option, Domain Runtime, provides access to the Domain Wide metrics and is available only for the Admin Server):

oracle weblogic book oracle weblogic books

Next, select the MBean you want to collect metrics for. For example, if you are behind JVM metrics, select ‘weblogic.management.runtime.JVMRuntimeMBean’ as shown:

oracle weblogic book oracle weblogic books

In the next screen, specify which attribute of the MBean you want to monitor. In our case, we will select ‘HeapSizeMax and click “Finish”.

oracle weblogic book oracle weblogic books

Finally, from the summary view of WLDF Modules, select the target instance which you want to monitor (for example WLSNode1) and click Finish.

Francesco Google+