Optimize 10.5 | webMethods Optimize Documentation | Using webMethods Optimize | Defining Rules | Setting Rule Attributes
 
Setting Rule Attributes
The Attributes panel on the Add/Edit/Copy Rule page enables you to specify attributes for a rule.
*To set attributes for a rule
In the Attributes panel, do the following:
1. From the Rule Type list, select one of the rule types.
Important:
If you change the rule type for an existing rule, Optimize erases the rule expression. Also, if you change either the rule type or the rule expression itself, Optimize removes all previous rule instances and violations, and creates new rule instances for the rule to match the KPI instances in the revised rule expression.
The following table describes the rule types.
Rule Type
Description
KPI
Evaluates one or more KPIs at the KPI's collection interval. For more information about creating KPIs, see Administering webMethods Optimize.
Event
Evaluates data points as they are collected rather than waiting for a KPI collection interval.
Threshold
Evaluates a single collected data point at the time of collection.
See Types of Rules for a complete description of these rule types.
2. If you want the rule to be enabled when you save it, select the Enabled check box. If you want the rule to be disabled when you save it, clear the check box.
3. If you want to make the rule sticky, select the Sticky check box. A sticky rule does not acknowledge that a violated rule's data has come back into compliance until the rule is manually resolved as described in Viewing Information About Rules in this guide. You can make a rule sticky to signal a serious violation that requires user attention to remedy the situation. For example, if you create a rule to detect that a Broker Server is offline, defining the rule as sticky causes the alert to occur once and the rule to remain in violation until the rule is resolved by clicking Resolve on the Rule Detail page.
Important:
If a sticky rule is violated again before being resolved, Optimize cannot detect those violations.
4. If you want this rule to contribute to the Six Sigma rule violation data displayed on the Improve page, select the Contributes to Six Sigma check box.
5. To specify that this rule is associated with a Service Level Agreement (SLA), select SLA. You can search for SLA rules on the Problems and System Overview pages so that you can easily find problems and resources related to your SLA-specific rules.
6. Optionally specify the name of the customer associated with this rule (particularly useful if this is an SLA rule) in the Customer text box. You can also search for Customer on the Problems and System Overview pages so that you can easily find problems and resources related to your customer-specific rules.
7. If you want any specified alerts generated for this rule to be repeated, specify the number of minutes between alerts in the Reminder Interval text box.
8. If you want to be notified when this rule comes back into compliance after being in violation, select Send alerts/actions when back in compliance.
Tip:
You can sort rules by severity in the tables on the Problem Report and Analytics Overview pages. To ensure that rules with severity text sort appropriately, consider beginning the severity text string either with a number that indicates the level of severity or with an identical text string followed by a severity number. For example, you could use a severity text-string sequence such as 1 High, 2 Medium, 3 Low, and so on. Alternatively, you could use a severity text-string sequence such as Severity 1, Severity 2, Severity 3, and so on.