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 |
|
Configuration Options
This appendix describes configurable options for integrating Icinga with OpsCx for Icinga. All options are configured with default values you can modify.
Option | Description |
---|---|
Policy Parameters | |
Icinga_Hostname |
Icinga Domain Manager host name. |
Icinga_Port
|
Port where the Icinga Domain Manager listens to the REST call. Default: |
Icinga_Username
|
Icinga Domain Manager API user name. |
Icinga_Password |
Icinga Domain Manager API password. |
Event Integration Parameters | |
Copy_XML |
If enabled, it will copy the incoming raw data form Icinga domain server in XML format to the OpsCx system. The data files will get created in the location Default: |
Opscx_SSL_Usage |
Enable/Disable SSL usage for Event Integration. By default SSL Usage will be true. Default: |
Opscx_Port |
Port Configured for OpsCx. Default: |
UsePersistency
* |
If set to true, all incoming messages will first be persisted into a file-based store before sending them to the remote host. Default: The directory path, used for the persistence layer is You will find a text file that is prefixed with |
Log Level |
Log level for Event Integration. Default: |
Topology Integration | |
Topology Polling Interval |
Interval at which Topology data will be fetched from Icinga Domain Manager. The interval value is in seconds. Default: |
Opscx_SSL_Usage |
Enable/Disable SSL usage for Topology Integration. By default SSL Usage will be true. Default: |
Opscx_Port
|
Port Configured for OpsCx. Default: |
Copy_XML |
If enabled, it will copy the incoming raw data form Icinga domain server in XML format to the OpsCx system. The data files will get created in the location Default: |
DNS_Lookup
|
In some cases the Icinga responses may have missing host name or IP address. If enabled, this option will provide a look up of all the missing host name and IP address. Default: |
Log Level |
Log level for Topology Integration. Default: |
Backward Synchronization Parameters | |
Icinga_Acknowledge_Comment
|
Comment for acknowledging the events from OMi. Value: |
Icinga_Acknowledgement_Author
|
Author of the event acknowledgment. Value: |
OMi_Base_URL
|
Set the OMi root URL as value. Example: This value will be used to construct the OMi event link and will be sent with the acknowledgment comment. Clicking on the link Click here to go to OMI Event will redirect to the corresponding closed event in OMi. If this value is not set, the OMi Event id will be sent with the acknowledgment comment. Value: No default value |
*The UsePersistency
option is useful when data from OpsCx is not reaching OMi.
About Persistency
If the connection between OpsCx and OMi is interrupted the data cannot reach to OMi. By setting the UsePersistency
field to TRUE
, a copy of original data is persisted in tmp
files. Once the connection is resumed, the data from the persisted files is sent to OMi. The maximum capacity of tmp
file is 4 MB. After the file attains the maximum capacity, roll-over happens and a new file is created.
If data from the previous persistency file has not been sent to OMi, there will be a reference to old persistent file in the same folder. Once connection with OMi is resumed, those messages will be sent to OMi along with new messages, from the new file.
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: