As a Application Server admin,
it is always complex to me to monitor various servers , cluster and even
resources deployed to servers in a weblogic. There is a need for some
technology which will do the monitoring for me and send me the alerts when a
resource is down.
The Weblogic Diagnostic
Framework (WLDF ) which is a part of the weblogic Server allows to send
notifications when certain contains are detected. This allows us to configure
rules which match runtime conditions and when met send notifications.
The major components are
- Diagnostic Image Capture: This created a
Diagnostic Snapshot from the serer that can be used for analysis
- Archive: captures and persists data events, log records and metrics
from server instances and applications.
- 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.
Oracle Weblogic Diagnostic
Module
As said earlier, a diagnostic module allows creating a diagnostic
snapshot from the server that can be used as a post-failure analysis. In this
post we will see how we can create a diagnostic module.
1. Click on the Diagnostic Modules in the Weblogic Console
2. In the next Screen, enter the name for the Diagnostic Module. Save
Even though the Diagnostic module was created, it did not have any
metrics enabled. Click
on the newly Created Diagnostic module and select the Configuration tab
and Collected Metrics sub tab.
3. Click New in the Configuration tab.
4. In the next screen we can 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)
5. In the next screen, select the MBean type “weblogic.management.runtime.JVMRuntimeMBean”
6. In the next screen, select the attribute of the Mbean you want to
collect.
7. Select
‘HeapSizeMax’ and click “Finish”.
Finally select the target instance which you want to monitor and click
Finish.
More to Come , Happy Learning