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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Integrate > Icinga

Icinga

Icinga is an open source monitoring system which checks the availability of your network resources, notifies users of outages, and generates performance data for reporting. Operations Connector for Icinga (OpsCx for Icinga) integrates Icinga and Operations Manager i (OMi) so that the gathered systems-management data about the events and topology in an Icinga environment is made available to the OMi solution. Such data can then be monitored and processed properly within OMi. OpsCx for Icinga therefore enables you to establish a link between an Icinga environment and operations management in OMi.

For a list of the OpsCx for Icinga products and their release versions that Operations Connector supports, see Supported Icinga Versions topic.

For information about Icinga products, their individual releases and features, see the documentation on the Icinga website.

Key concepts

OpsCx for Icinga is a product complementary to Operations Connector (OpsCx). It enhances OpsCx to provide the following functionality:

Collection of Icinga events and topology data from an Icinga environment.
Mapping of the collected data to an OMi-compliant form.
Customization of the data collection and data mapping.
Acknowledgment of Icinga events from OMi by using backward synchronization of the event resolution states.

OpsCx for Icinga supports cluster environment of OpsCx system. For more information on OpsCx cluster environment, see Operations Connector User section.

Event Collection and Forwarding

OpsCx for Icinga makes Icinga events available to OMi as follows:

Events are received from Icinga through the icinga web service via REST API.
In OpsCx for Icinga, the received events are processed and sent to the REST Web Service endpoint of OpsCx.
The collected events are mapped with a OpsCx for Icinga policy of the REST Web Service Listener type, and then forwarded to OMi.
The Event Alerts from Icinga with event type Statechange are collected and forwarded to OMi.

OpsCx for Icinga enables tracing of Icinga alert that triggers an OMi event. It also supports close-state propagation of events. Whenever an alert is closed in Icinga, the corresponding event in OMi is also closed. Additionally, if backward synchronization of event resolution states is enabled, for each event that you close in OMi the corresponding Icinga alert is acknowledged. Other alert updates are not propagated back to Icinga.

Topology Collection and Forwarding

OpsCx for Icinga makes Icinga topology available to OMi as follows:

Topology data are received from Icinga through the icinga web service through REST API.

OpsCx for Icinga identifies hostnames and IP addresses from the REST API and forwards topology data to OMi.
The constructed topology data is mapped by using a OpsCx policy, and then forwarded to OMi.

The following CI types are created by default:

Nodes: UNIX, Linux, or Windows systems are node CIs that are discovered by Icinga.
IP addresses: By default, CIs are created for the IPv4 or IPv6 address of a node.

The following table shows how Icinga topology data is mapped:

Icinga Type	OMi CI Type	Topology Map
Host Group	CI Collection
Host	Computer
`IPaddress` attribute of a Host	IP address

Product Limitations

This section describes known limitations in OpsCx for Icinga:

Event forwarding to OMi

During downtime of OpsCx server, the Icinga alerts generated are not collected and forwarded to OMi even after the OpsCx server is restarted. However, new alerts generated gets forwarded.

Icinga

Key concepts

Event Collection and Forwarding

Topology Collection and Forwarding

Product Limitations

Related topics