
Chapter 12
Threshold Alarms
12.1 Introduction
To supplement the standard alarms raised by Rhino, an administrator may configure additional alarms to be raised or cleared
automatically based on the evaluation of a set of conditions using input from Rhino’s statistics facility. These alarms are known
as Threshold Alarms and are configured using the Threshold Rules MBean.
This chapter describes the types of conditions available for use with threshold alarms and provides an example demonstrating
configuration of a threshold alarm.
12.2 Threshold Rules
Each threshold rule consists of the following elements:
• A unique name identifying the rule.
• A set of trigger conditions containing at least one condition.
• An alarm level, type and message text.
• Optionally, a set of reset conditions.
• Optionally, a time period in milliseconds for which the trigger conditions must remain before an alarm will be raised.
• Optionally, a time period in milliseconds for which the reset conditions must remain before an alarm will be cleared.
Condition sets may be combined using either an
AND
or an
OR
operator. When
AND
is used all conditions in the set must be
satisfied; when
OR
is used any one of the conditions may cause the alarm to be raised or cleared.
12.3 Parameter Sets
The parameter sets used by threshold rules are the same as used by the statistics client. The parameter sets can be discovered
either by using the statistics client graphically, or by using its command-line version from a sh or bash shell as follows:
$ client/bin/rhino-stats -l
2006-01-10 17:33:42.242 INFO [rhinostat] Connecting to localhost:1199
The following parameter set types are available for instrumentation:
Activities, ActivityHandler, CPU-usage, ETSI-INAP-CS1Conductor,
Events, License Accounting, Lock Managers, MemDB-Local,
MemDB-Replicated, Object Pools, Savanna-Protocol, Services, Staging
Threads, System Info, Transactions
78
Komentarze do niniejszej Instrukcji