Monitoring WebLogic Server 12c - Oracle WebLogic Server 12c Advanced Administration - page 167

The WLDF archive can use a JDBC-based store to persist
the collected data.
The scenario of 100 queued requests waiting to be processed can indicate a potential
problem because all threads of the WebLogic Server thread pool could be busy and the
requests will not be processed fast enough, causing the incoming requests to pile up. The
EmailAlertWatch watch was created for such situations to observe when the QueueLength
value is greater than 100 . When this condition is reached, the watch triggers an event to the
EmailAlertNotification notification and an e-mail is sent to the specified recipients.
The notification can also be configured as an SNMP trap, a JMS message, a JMX operation,
or a Diagnostic Image.
The WLDF is very flexible and can be configured with any attribute
of the exposed MBean. Set up a watch expression that meets the
condition and the monitoring requirements of your environment.
See also
F Generating a SNMP trap
F Viewing historical data in the monitoring dashboard using a database
Generating an SNMP trap
WebLogic provides Simple Network Management Protocol (SNMP) standards to monitor the
domain, Managed Servers, and applications the same way the exposed MBean's attributes
were monitored in the last recipe using WLDF.
In this recipe, an SNMP agent will be added to monitor all Managed Servers of the PROD_
Domain , watching for the same QueueLength attribute of the ThreadPoolRuntime MBean.
An SNMP trap will be triggered by adding a gauge monitor to verify if the QueueLength value
is above 100 .
Getting ready
The Server SNMP agent called PROD_SNMPAgent will be created using the Administration
Console, so make sure the Administration Server is running.
This recipe assumes there is an SNMP Manager listening for an SNMP trap at the hostname
snmphost on port 162.