Use > Monitor health

Monitor health

OMi enables you to monitor the availability and performance of the applications and services in your organization. You can keep track of your applications' and services' health, and OMi informs you about problems it detects.

OMi uses data collected by HPE Software applications, such as OM and HPE Operations Agent, as well as data collected from external monitoring tools. Events are displayed based on the collected data received from a range of environments, including Cloud, ERP, Web, and SAP, and from a range of back-end infrastructure components, including web servers, J2EE applications, databases, and network and storage devices.

The collected and aggregated data is used by health indicators (HIs) and key performance indicators (KPIs) to provide quantifiable measurements that help you monitor how well your business is achieving objectives. The KPIs and HIs provide assessment of the present state of your business and processes, enable you to track critical performance variables over time, and help you assess the business impact of problems in the system.

At the top level, OMi provides an integrated view of critical applications and business processes; from there, you can drill down to the underlying IT infrastructure associated with these critical business processes. This drill-down view can be laid out in any number of ways, such as by data centers, by technology clusters, by geographical locations, and so on.

The following graphic shows how the basic Service Health components impact each other:

Service Health components

KPIs (key performance indicators) represent the overall status of CIs. A CI's status is driven by the worst status of all KPIs. They are high-level indicators of CI performance and availability. Based on business rules, the KPI status is calculated by using the statuses of one or more HIs, one or more KPIs, or a combination of both.


A software application CI has multiple KPIs assigned, including a Software Availability KPI. This KPI can be used to represent the up or down status of all running software CIs.

HIs (health indicators) are fine-grained measurements that reflect the state of a CI based on a particular operating characteristic. A change in a health indicator state can affect the KPI status, as well as the ETI status of a CI.

ETIs (event type indicators) are categorizations of events. As multiple data collectors may send event samples regarding a single event to OMi, events are generalized into a common type.

Once an event arrives in OMi, it is mapped to a CI, and subsequently to an ETI. If configured, the HI values are attached to the CI and the CI's KPI status is calculated based on those HIs. In the last step, the event correlation is calculated based on topology-based event correlation (TBEC) rules, and the event is displayed in the OMi Event Browser.