Troubleshooting the Collection of Events and Topology

When unexpected events (alerts) or topology appear in OpsCx for Icinga or you miss specific OpsCx for Icinga entities, the root cause of the problem may be improper integration configuration, or some other reason. To ease the inspection of data flow between Icinga and OpsCx, OpsCx for Icinga can create output files with collected events (alerts) and topology. Such output files contain the XML formatted data acquired from the integrated OpsCx for Icinga instance, but they are not used in data forwarding to OpsCx for Icinga.

To generate the event or topology output file on the OpsCx for Icinga host, perform the following steps:

1. Log on to the OMi console.
2. Go to Administration > Monitoring > Assignment & tuning.

3. From Select a view drop-down box, click Operations Connectors. The left pane with the list of OpsCx system(s) appears.

4. Click on the OpsCx system. The Assigned Item lists the OpsConnector for Icinga Management Templatefor the selected system.
5. In Assignment Details tab, click icon to see the list of Expert Parameters.
6. Double-click on Log Level parameter. The Edit Parameter: Log Level pop-up appears
7. In the drop-down list select DEBUG log level and click OK.
8. Double-click on Copy_XML parameter. The Edit Parameter: Log Level pop-up appears
9. In the drop-down list select TRUE and click OK.
10. Restart the ICINGA service. For steps, see Managing the Integration Service topic.

Related topics

Managing the Integration Service