Administration > Application Administration > Dashboard Administration > Configuring KPIs > About Business Rules
About Business Rules
A KPI must always have an associated business rule that defines the logic to be performed (by the Business Logic Engine) to calculate the measurement for the KPI. The properties and objectives that are assigned to the KPI depend on the selected rule.
Mercury Business Availability Center provides predefined rules for use with the KPIs. The rules are defined in the Business Rules Repository, where you can edit the rules, or create customized rules. For information on the business rules available in Dashboard, the roles they play, and how to edit them, see Business Rules Repository.
Some business rules are specific to a particular KPI, while others can be used for a variety of KPIs. In the KPIs Repository, each KPI has a defined default rule, and a list of rules that can be used with that KPI. (If required, the default rule and the allowed rule list can be modified. For details, see Configuring KPIs.)
When a CI is created by the source adapters in Source Manager, it is assigned KPIs and business rules according to the adapter definitions. When a KPI is added manually to a CI in the KPIs tab, it is assigned the default business rule defined for the KPI (the default rule is usually a rule for groups). For example, for the RT Impact KPI, there are two applicable rules: Real Time Impact Rule and Sum of Values Rule. When you add a new RT Impact KPI to a CI, the default rule for the KPI, Sum of Values Rule, is automatically assigned. You can change the assigned rule when adding or editing the KPI in the KPIs tab, by selecting a new rule from the list of allowed rules for the KPI.
There are two categories of business rule, monitor rules and group rules, as described in the following sections. Most KPIs work with at least one rule from each category.
Monitor Rules
Monitor rules (also called leaf rules) are business rules that are applied to leaf CIs of monitor type. Monitor rules are used to calculate a measurement for the KPI based on original sample data that is caught by the KPI selector. For example, the RUM Page Monitor Availability Rule calculates the Availability KPI for RUM Page Monitor CIs, based on the sample data received from Real User Monitor.
A monitoring CI is intended to receive incoming metrics, generally received via one of the data collectors, such as SiteScope, Business Process Monitor, or Real User Monitor. Monitoring CIs are automatically added to the Mercury Universal CMDB by the source adapters in Source Manager, according to the monitoring definitions. These monitoring CIs have default KPIs that use a monitor rule, and predefined selectors.
In general, the leaf CIs in a subtree (the CIs that form the lowest level of the hierarchy) should always be one of the monitoring CIs. When creating new subtrees in your views in IT Universe Manager, you attach monitoring CIs created by the source adapters as leaf nodes, and these CIs then pass KPI status up the hierarchy.
Group Rules
Group rules are business rules that determine KPI status based on data received from other KPIs, rather than from original sample data. The received data may come from the KPIs of child CIs, or from another KPI associated with the same CI.
Note: Even though this category are called group rules, some of them are also applicable for monitoring/leaf level CIs. For example, the Impact Over Time Rule (used with the OT Impact KPI) can be used with a group CI or a monitoring CI. What all rules in this category have in common is that their status calculations are contingent on data received from other KPI instances, rather than from the samples.
The group rules vary in the type of logic they use to arrive at a status result. For example:
- the rule may select a KPI status held by one of the child CIs, and apply that status to the parent, as done by the Worst Child Rule.
- the rule may aggregate the received data to calculate a measurement, and compare the measurement with defined objectives, as done by the Sum of Values Rule.
- the rule may calculate a measurement based on the status of another KPI for the CI, and compare the measurement with defined objectives, as done by the Real Time Impact Rule when receiving status from the Availability KPI.
| Copyright 2006 Mercury Interactive Corporation |