Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Use
- Navigate OMi
- Log into OMi
- Change your name and time zone
- Work with events
- Use the Event Browser
- Use the Event Browser (HTML)
- Use the Actions pane
- Browse CIs with the CI Explorer
- Specify tools
- Define and manage views
- Monitor health
- Customize My Workspace
- Work with dashboards
- Use the Operations Console
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:
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.
Example
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.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: