SNMP Counter Monitors: Configuration
Configuration Options Related Tasks Related Topics
Use this page to configure a counter monitor, which periodically polls an attribute whose value is an integer and compares the attribute value with a high threshold that you define. A counter monitor generates a trap if the attribute value equals or exceeds the high threshold. You can also configure an offset or modulus, which increases or decreases the threshold each time the threshold is crossed.
Name Description Name
The name of this counter monitor.
Each monitor within a domain must have a unique name.
The name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the monitor.
After you have created a monitor, you cannot change its name. Instead, delete it and create a new one.
Monitored MBean Type
The MBean type that defines the attribute you want to monitor. Do not include the
MBeansuffix. For example,
Monitored MBean Name
The name of the MBean instance that you want to monitor. If you leave the name undefined, WebLogic Server monitors all instances of the MBean type that you specify in Monitored MBean Type.
Do not enter the full JMX object name of the MBean instance. Instead, enter only the value of the object name's
Name=namename-value pair. To create unique MBean object names, WebLogic Server encodes several name-value pairs into each object name. One of these pairs is
Name=name. For example:
In the previous example, specify
MedRecServeras the name of the MBean instance.
User Entered MBean Name
User Entered MBean Name.
Monitored Attribute Name
The name of an MBean attribute to monitor. This attribute must be in the WebLogic Server MIB.
The frequency (in seconds) that WebLogic Server checks the attribute value.
Specifies a value that triggers the Counter Monitor to generate a trap.
The Counter Monitor generates a trap each time it polls the value and determines that the value has transitioned from below the threshold to at or above the threshold. While the value remains at or above the threshold, the Counter Monitor does not generate additional traps.
If the threshold is 0, the counter monitor to generates a trap each time it polls the value, unless the value is negative.
An integer value to be added to the threshold value when the threshold is crossed.
If Offset is
0, a trap is generated each time the agent polls the monitored attribute and its value still exceeds or equals the value in the Threshold.
If Offset is larger than
0, the value of the offset is added to the threshold each time the threshold is crossed.
For example, if you set Threshold to 1000 and Offset to 2000, when the observed attribute exceeds 1000, the Counter Monitor sends a notification and increases the threshold to 3000. When the observed attribute exceeds 3000, the Counter Monitor sends a notification and increases the threshold again to 5000.
An integer value to be subtracted from the threshold value when the threshold value is crossed.
If Modulus is 0, a trap is generated each time the agent polls the monitored attribute and its value still exceeds or equals the threshold value.
If Modulus is larger than 0, the value of the modulus is subtracted from the threshold each time the threshold is crossed.
- Create counter monitors
- Determine MBean instance names
- Determine MBean types and attribute names
- Target counter monitors
- Verify trap generation