Troubleshoot the Collection of Events and Metrics

When unexpected events (alerts) or metrics appear in OMi or you miss specific VROPS entities, the root cause of the problem may be improper integration configuration, inadequate definition of entity mapping or rules in the corresponding Operations Connector policies, or some other reason. To ease the inspection of data flow between VROPS and Operations Connector, OpsCx for VROPS can create output files with collected events (alerts) and metrics. Such output files contain the XML formatted data acquired from VROPS, but they are not used in data forwarding to Operations Connector.

Because the topology integration of OpsCx for VROPS uses a different data relaying pipeline, this troubleshooting method is not available for VROPS topology.

To generate the event or metric output file on the Operations Connector host, perform the following steps:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntVROps and open the appropriate integration configuration file in a plain text editor.

2. In the pipe section, uncomment the line with the following definition:

   • Event integration: splitter -1-> xmleventsink

   • Metric integration: splitter -1-> metricxmlsink

3. Optional: To fine‑tune the output file generation, adjust the options in the following subsection of the nodes section:

   • Event integration: sink (xmleventsink)

   • Metric integration: sink (metricxmlsink)

4. Save your changes.

5. Restart the affected integration service as described in Restarting the Services topic.

The output file with the XML-formatted event or metric data is created at the location defined with the filename option in the integration configuration file.

Related topics

Restarting the Services