|
 |
| e-docs > WebLogic Server > WebLogic SNMP MIB Reference > BEA WebLogic Server Traps MIB |
|
WebLogic SNMP MIB Reference
|
The WebLogic Server Traps MIB describes the information returned by the WebLogic Administration Server SNMP Service for trap notifications. This section includes the following topics:
The SNMP trap notification data packet (PDU) includes a series of name/value pairs in the Variable Bindings field that contain additional information about the trap.
This section describes the variables that can be included within the variable bindings of traps generated by the WebLogic SNMP agent.
A string that indicates the time when the trap notification was generated.
The name of the server that generated the trap.
The machine where the trap was generated.
An integer that indicates the id of the thread in which the log message was generated. This is derived from the log message attribute.
The id of the transaction from which the trap is generated (if any). This is derived from the transaction id of the log message.
The user id from which the trap is generated. This is derived from the user id of the log message from which the trap is generated.
The subsystem from which the trap is generated. This is derived from the subsystem attribute of the log message.
The message id of the log message from which the trap is derived.
The severity of the log message from which the trap is derived.
The body of the log message from which this trap is derived.
The string should be either CounterMonitor, or GaugeMonitor, or StringMonitor. This indicates the type of JMX monitor that generated the trap.
An ASCII-string representation of the value that was used to define the threshold. A detected value that varies appropriately from this value is what will trigger the trap.
This is the detected value that crossed the threshold defined for the monitor.
When an attribute change trap is generated, this is the name of the MBean for that attribute.
When an attribute change trap is generated, this is the type of the MBean for that attribute.
When an attribute change trap is generated, this is the type of the attribute whose change triggered the trap.
When an attribute change trap is generated, this is the type of change that has occurred. The value can be either ADD, UPDATE, or REMOVE.
The value of the attribute prior to the change.
The value of an attribute after the change.
This section defines all the traps that can be generated by the WebLogic SNMP agent.
The following attributes are included in the Variable Bindings: trapTime, trapServerName, trapMBeanName, trapMBeanType, trapAttributeName, trapAttributeType, trapAttributeChangeType, trapAttributeOldVal, trapAttributeNewVal
This trap occurs if the SNMP agent has been configured to detect a change on a specified attribute and send notification of a change, and a change has occurred on the specified attribute.
The following attributes are included in the variable bindings: trapTime, trapServerName, trapMachineName, trapLogThreadId, trapLogTransactionId, trapLogUserId, trapLogSubsystem, trapLogMsgId, trapLogSeverity, trapLogMessage.
This trap occurs if the SNMP agent has registered a log notification filter on a Managed Server and a log message has occurred that matches the filter. The textual description and severity of the log message indicates the appropriate action to take.
The following attributes are included in the variable bindings: trapTime, trapServerName, trapMonitorType, trapMonitorThreshold, trapMonitorValue, trapMBeanName, trapMBeanType, trapAttributeName.
This trap occurs if a JMX monitor has been configured and the monitor detects a condition on the monitored resource that crosses the threshold or satsifies the condition defined for that monitor. The attribute being monitored is indicated by trapAttributeName.
The attributes included in the Variable Bindings are: trapTime, trapServerName.
The Managed Server indicated by trapServerName has shutdown.
The attributes included in the Variable Bindings are: trapTime, trapServerName.
The Managed Server indicated by trapServerName has started.
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
