Use > Monitor health > HI-based KPI calculations

HI-based KPI calculations

HIs provide the data that a KPI needs to calculate the availability and performance of monitored resources. The KPIs use calculation rules to collate the values from multiple health indicators and set a severity status on the KPI for a specific CI, such as: Critical, Major, Minor, or Normal. For example, a Software Performance KPI for a database can include multiple health indicators concerning the cache-hit ratio (0, 50, 00%), the length of query queues (Empty, Full), and response times (#ms) to determine the overall software performance.

The color of each KPI reflects the KPI's current severity status. The severity status is determined by a business rule, which specifies how and when severity status propagates up a relationship chain. One resource with a critical problem does not mean that all dependent resources are, by definition, also critical. KPIs can use data from multiple sources to determine the overall effects up and down dependency chains and determine the severity status accordingly.

Note The type of source determines the importance of the information provided. For example, live data from a monitor running directly on a node is considered more important than data resulting from business rules, which base calculations on KPI relationships and dependencies. This means that KPI states propagated by a business rule may be overridden by KPI states calculated from HIs directly on the CI.

KPIs related to the CI of a selected event are displayed in the Health Indicators pane of the Health Perspective tab. In the Health Top View, KPIs appear under the monitored object to which they belong. Additionally, you can use the 360° View page to display a hierarchy of CIs in a view, the KPIs assigned to each CI, and their KPI statuses.
For a list of all Service Health components, see Service Health Components.

Learn More

Tasks