Administration > Application Administration > Dashboard Administration > Configuring KPIs > Introducing KPI Configuration
Introducing KPI Configuration
The Dashboard KPIs (Key Performance Indicators) provide quantifiable measurements that help you monitor in real-time how well your business is achieving its objectives. They provide real-time status for the CIs representing your business and processes, enabling you to assess the business impact of problems in the system.
Each KPI works with a predefined set of values, against which the incoming metrics are measured. The resulting measurement for the KPI is translated into a color-coded status indicator, displayed in the Dashboard Console, where the color represents a more desirable or less desirable condition for the KPI. You can learn more about KPI functionality in How Dashboard KPIs Work.
CIs can have multiple KPIs attached. KPIs can be attached to a CI as follows:
- KPIs may be attached to the CI as part of the CI creation.
- For CIs created by the source adapters in Source Manager, all CIs are automatically assigned default KPIs, according to the nature of the CI. For example, a CI for a Business Process Monitor profile has default KPIs for Availability and Performance. For more information on the source adapters and how they define the default KPIs, see Source Manager Administration.
- CIs that are added manually or by Discovery Manager do not have automatically assigned KPIs. For information on how Discovery Manager creates CIs, see Discovery Manager Administration.
- KPIs may be attached to a CI as a result of propagation from child CIs. Most KPIs propagate up through the hierarchy, so that parent CIs have the same KPIs as all their child CIs.
- KPIs may be manually attached to a CI in the Dashboard Administration KPIs tab. You may want to attach new KPIs to a CI, in addition to the default/propagated KPIs, to broaden the information derived from the monitoring measurements. For example, you can add an OT Impact KPI to assess the ongoing cost of an application that is not available.
In the KPIs tab, as well as attaching new KPIs to a CI, you can edit existing KPIs and delete attached KPIs.
Notes and Limitations
- You must create at least one Mercury Business Availability Center profile database in order for Dashboard to receive data samples. For details on how to do this, see Database Administration in Platform Administration.
- Any change you make to the KPIs for a CI—adding new KPIs, deleting KPIs, or editing KPI properties—will change the CI in the Mercury Universal CMDB, meaning that the changes will be seen in any view that the CI appears.
- There are no restrictions on the type of KPI that can be attached to a CI, or on the type of business rule that you can select from the allowed rules list for a KPI. You must ensure that you select KPIs and business rules that are appropriate for the CI type.
- The Application KPI is only applicable for CIs corresponding to Mercury Diagnostics (and is attached automatically to Mercury Diagnostics CIs when Mercury Diagnostics is supported in Mercury Business Availability Center). For more information, refer to the Mercury Diagnostics Installation and User's Guide.
- KPIs that are added to a CI as part of a SLA definition in Service Level Management Administration have no relevance to the Dashboard KPIs and do not appear in the KPIs tab. Conversely, KPIs added to a CI in the KPIs tab have no relevance for the CI when it is included in an SLA, and do not appear for the CI in Service Level Management.
- Deleting a KPI may impact on other KPIs that are dependant on the first KPI. For example, OT Impact is calculated based on the status of another KPI, such as Availability; in this case, deleting the Availability KPI would prevent calculation of OT Impact.
- KPIs that were created for CIs by the source adapter templates, frequently have objective values that differ from the default ones used by the business rule. However, when editing one of these KPIs, if you select a different rule and then revert to the original rule, then the original objective values are replaced with the rule default values.
| Copyright 2006 Mercury Interactive Corporation |