Before you begin
A counter monitor periodically checks the value of an integer attribute and generates a trap when the value exceeds a threshold. You can also configure a counter monitor to increase the threshold by an offset value after it sends a trap.
Note: Once you create a counter monitor, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
For more information, refer to Determine MBean types and attribute names.
If you do not enter an instance name, the monitor observes all MBean instances of the type that you specified in Step 4.
For testing purposes, consider entering a small value, such as 10.
A value of 0 means that the monitor never polls the attribute, effectively disabling this monitor.
For example:
Each time the observed attribute exceeds the new threshold, the threshold is increased by the offset value. 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.
To specify a maximum value for the threshold, enter a value in the Modulus field. When the threshold reaches the value specified by the modulus, the threshold is returned to the value that was specified through the latest call to the monitor's setThreshold method, before any offsets were applied. For example, if the original Threshold is set to 1000 and the Modulus is set to 5000, when the Threshold exceeds 5000, the monitor sends a notification and resets the Threshold to 1000.
For more information about these fields, see Configuration Options.
After you finish
You do not need to restart the Administration Server after you create and initially configure a monitor. However, if you change a monitor after you create it, you must restart the Administration Server.