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 |
|
- Topology-Based Event Correlation
- Topology-Based Event Correlation Overview
- Correlation Rules
- Cross-Domain Event Correlation
- Event Correlation Rule topology
- Correlation Rule symptoms and causes
- Correlation Rule weighting
- Configure Topology-based Event Correlation Rules
- Create Event Correlation Rules
- Select Topology Views
- Define the Rule Topology
- Specify Correlation Rule Symptoms
- Specify Correlation Rule Causes
- Set the Correlation Time Limit
- Set the Correlation Auto-Extend Time
- Correlation Rules User Interface
Cross-Domain Event Correlation
The Correlation Rules manager enables you to set up rules that correlate indicators for configuration item types in multiple and different domains, for example, database, storage, and web application. Cross-domain correlation connects a chain of rules that are defined in different domains. The correlation process can use the symptom of one rule as the cause of the next rule in the chain, or vice versa.
The link between correlation rules in different domains is the same indicator state assigned to the same configuration item type. In one rule, you can define an indicator state as a symptom for a specific configuration item type. In another rule for a different domain, you can define the same indicator state as a cause for the same configuration item type. If all the events occur in the different domains as expected and trigger correlation rules, the correlation process displays in the Event Browser only the cause event from the last rule in the event correlation chain.
Note Cross-domain correlation rules must share at least one identical combination of configuration item type and indicator state.
For example, if all the necessary correlation rules are defined for the database, storage, and web application domains, and the necessary indicator states are being monitored for a shared configuration item, the Correlation Rules manager can determine that a problem with physical disk utilization in the storage domain is the cause of the problem concerning the availability of the web server.
The Correlation Rules pane in the Correlation Rules manager incorporates a list of correlation rules containing symptoms or states that also feature in rules defined for a different domain. In cross-domain rules, indicator states configured as a symptom in one rule are also defined as a cause in a rule defined in another domain. You can choose whether to view rules that determine the symptom or the cause of an event and expand the item to see if the rule is part of a chain.
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: