Field | Description | |
Name | Descriptive name for the rule you are creating. | |
Apply To | Click the appropriate check box to indicate whether you want this rule to apply to the selected KPI instance only or to all KPI instances. | |
Send Alert To | Enables you to specify a user who will receive an alert message if the rule is violated. This field is unavailable if the currently logged in user hasn’t specified an e-mail address in the user settings. | |
Action | Enables you to specify a system action to invoke automatically if the rule is violated. | |
Execute On | Enables you to specify whether the rule should fire on a KPI interval (KPI-Aggregation Interval) or on an actual event (Event-Every Event Occurrence). | |
Expression Type | Enables you to specify the type of expression to be used with this rule. The actual expression is defined in the Condition field below. The Expression Type options are as follows: Reading Value: Enables you to create a rule violation condition statement based on a user-selected comparator and value. Normality: Enables you to create a rule violation condition statement based on values being one or two standard deviations above or below the mean value. Trending: Enables you to create a rule violation condition statement based on a value that is trending up or down for a specified duration. | |
Condition | This field enables you to formulate the expression that determines the specific conditions under which a rule will fire.... | |
For expression type | Complete these fields | |
Reading Value | Choose a comparison operator from the Comparison drop-down list and specify a value in the Value field. | |
Normality | Choose the appropriate radio button. | |
Trending | Choose either Trends Up or Trends Down and specify a whole integer of intervals in the Duration field. | |
Generate historical rule violations (may take some time to process) | Click this check box if you want the system to go through all legacy data and generate historical rule violations as appropriate. CAUTION: If you elect to generate historical rule violations, be aware that the process will likely consume significant system resources for some time. Be sure to plan accordingly. |