'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Monitor Java Management Extensions (JMX) MBeans > JMX monitors > Take Action commands for JMX monitors IBM Tivoli Monitoring, Version 6.3
JMX Add Counter Metric Watcher
Use this Take Action command to create a monitor to watch a counter attribute.
Parameters
- MBean pattern
- All MBeans matching this pattern are monitored by this monitor.
- Observed attribute
- Name of the MBean string attribute that is being watched.
- Initial threshold
- Value that the observed attribute is compared.
- Offset
- Value added to the threshold after the threshold is exceeded to create a changed threshold.
- Modulus
- Maximum value of counter after which it rolls over to 0.
- Difference mode
- True if the value monitored is the difference between the actual current and previous values of the attribute. False if the value monitored is the actual current value of the attribute (defaults to false). This mode effectively turns on rate-of-change monitoring.
- Granularity period
- Frequency with which measurements are taken (defaults to 20 seconds). Most important if difference mode is true
Example: Request a notification when any server has three or more errors
COUNTER_METRIC_WATCHER [*:j2eeType=Servlet,*] [errorCount] [3] [4] [] [diff] [gran]Where:
- *:j2eeType=Servlet,*
- MBean pattern: Monitors any J2EE servlet MBean whose name has a single key property named type whose value is ServerInfo
- errorCount
- Observed attribute: Increasing numeric attribute, this one indicating the number of errors of the servlet.
- 3
- Initial threshold: You want to be notified when errorCount meets or exceeds 3.
- 4
- Offset: When you get a notification for three errors, 4 is to the previous threshold of 3 to make a new threshold of 7. A second notification will be sent after errorCount reaches 7; a third at 11; a fourth at 15, and so on. Zero or none is not valid because it expects the counter to always increase and not increasing the offset would not make sense for a counter.
- Modulus:
- errorCount has no architected maximum value, so use an unreasonably high value.
- false
- Difference mode: You are concerned with absolute error counts. Difference is true if you are interested in the rate that errorCount was increasing.
- Granularity period: Not set, so take the default granularity period of 20 seconds. Granularity period is available for all monitor types. However, it is shown with a counter monitor so that a meaningful rate of change (with difference mode=true) can be determined.
Parent topic:
Take Action commands for JMX monitors