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

3. Select the QueueLength option from the Monitored Attribute Name drop-down
menu and click on the Finish button.
4. Click on the newly created QueueLengthGauge gauge and type 100 in the
Threshold High field. Click on the Save button.
5. Click on the Servers tab and enable the PROD_Server01 , PROD_Server02 ,
PROD_Server03 , and PROD_Server04 checkboxes. Click on the Save button.
6. Go to Diagnostics | SNMP on the left tree again and click on the
PROD_SNMPAgent link.
7. Click on the Trap Destinations tab and click on the New button.
8. Type QueueLengthTrap in the Name field. Type snmphost in the Host field
and 162 in the Port field. Click on the OK button.
9. Click on the Activate Changes button to finish.
How it works...
The same notification from the previous recipe was created, but in this recipe instead
of sending an e-mail alert using WLDF, a SNMP trap is generated to a hypothetical SNMP
Manager running at snmphost on port 162 .
The threshold condition is the same. The SNMP trap is sent when the QueueLength
attribute from the WebLogic thread pool from a Managed Server of the PROD_Cluster
value is above 100 .
The trap generated has the following format:
--- Snmp Trap Received ---
Version : v1
Source : UdpEntity:<source_ip>:1610
Community : public
Enterprise : enterprises.140.625
AgentAddr : <source_ip>
TrapOID : enterprises.140.625.0.75
RawTrapOID : 1.3.6.1.4.1.140.625.0.75
Trap Objects : {
{ enterprises.140.625.100.5=Sun Nov 11 15:50:55 BRST 2012 }
{ enterprises.140.625.100.10=PROD_Server02 }
{ enterprises.140.625.100.55=jmx.monitor.gauge.high }
{ enterprises.140.625.100.60=100 }
{ enterprises.140.625.100.65=435 }
{ enterprises.140.625.100.70=com.bea:Name=ThreadPoolRuntime,Server
Runtime=PROD_Server02,Type=ThreadPoolRuntime }
{ enterprises.140.625.100.75=ThreadPoolRuntime }
{ enterprises.140.625.100.80=QueueLength }
}