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 |
|
- Policies
Database Policies (Events, Metrics, and Generic Output)
Database policies enable you to collect data from database tables used by third-party systems by performing a query through a JDBC connection.
The following are examples of data that can be integrated into OMi using database policies:
-
Events from monitoring applications event tables or views.
-
Data from monitoring applications metrics tables.
-
Generic output data from monitoring applications tables.
Database policies use a user defined SQL query, an initial value statement, and a static initial value (session variable). The query you provide is used to define a search criterion on the database and with the initial value statement and a set up session variable, you can provide initial values that you can use in filtering. Starting with OMi 10.00, you are no longer limited to a fixed set of SQL clauses but can write more complex queries as well.
For example, if you fetch a field that contains a time stamp, you can write an SQL query to process only data records that happened after the policy was activated. You can do so by setting an appropriate initial value statement that is executed when the policy is activated and then compare the values retrieved in the main SQL clause against this initial value. For details on how the queries are used to fetch and filter records, see Understanding How Data From an SQL Query is Processed topic.
You use defaults and rules to control the data that is sent from Operations Connector to OMi.
Related topics
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: