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
Correlation Rules
Use the Correlation Rules manager to view, define, and apply correlation rules. Correlation rules associate selected configuration item types with defined indicator states to trigger a correlation process. The correlation process results in the highlighting of one or more configuration items as causes.
Correlation rules require a combination of symptoms and causes. Both symptoms and causes are defined by selecting configuration item types. Each configuration item type (such as a DB2 database) that you specify as a potential symptom requires one or more indicators (for example, Run State
, or Availability
) to be defined for it. Each indicator must have a state (for example, up
, down
, or offline
). Configuration item types you choose as causes also require an indicator and a state.
For example, the information in the following table defines a simple correlation rule for a database instance. OMi displays cause events in the Event Browser and the symptom events in the Related Events tab of the Message Details pane.
Rule Type |
CI Type |
Event Type Indicator |
Event Type Indicator State |
---|---|---|---|
Symptom |
DB2 |
Network Availability |
Offline |
Symptom |
DB2 |
Buffer Hit Ratio |
Low |
Symptom |
Process |
Run state |
Down |
Cause |
DB Table Space |
Buffer Performance |
Slow |
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: