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 > Microsoft SCOM > Troubleshoot > Troubleshooting the Collection of Events and Metrics

Troubleshooting the Collection of Events and Metrics

When unexpected events (alerts) or metrics appear in OMi or you miss specific Microsoft SCOM 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 Microsoft SCOM and Operations Connector, OpsCx for Microsoft SCOM can create output files with collected events (alerts) and metrics. Such output files contain the XML formatted data acquired from the integrated Microsoft SCOM instance, but they are not used in data forwarding to Operations Connector.

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

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

Change the current directory to <OvDataDir>\conf\HPBsmIntSCOM\genint and open the appropriate integration configuration file in a plain text editor. To determine which configuration file to modify, see Integration Configuration Files topic.
In the processor subsection of the nodes section, change the value of the copy-count option to 1.
In the pipe section, uncomment the line with the following definition:
- For the event integration: splitter -1-> eventxmlsink
- For the metric integration: splitter -1-> metricxmlsink
Optional: To fine‑tune the output file generation, adjust the options in the following subsection of the nodes section:
- For the event integration: sink (eventxmlsink)
- For the metric integration: sink (metricxmlsink)
Save your changes.
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.

Troubleshooting the Collection of Events and Metrics

Related topics