Mappings Used in the Metric Integration

OpsCx for Microsoft SCOM comes with preconfigured metric mappings that you can customize. The metric mappings are defined in the Operations Connector policy for Microsoft SCOM metrics. To reconfigure them, make sure the policy is imported into Operations Connector, and then edit it in the Operations Connector web interface.

The collected metrics are related to the set of objects defined in the Operations Connector policy for Microsoft SCOM topology. To collect additional metrics from Microsoft SCOM, first import the appropriate management pack into Microsoft SCOM. For instructions, see Configuring the Topology Integration topic. Afterward, select the additional metrics as described in Configuring the Metric Integration topic.

The Windows Server Operating System management pack consists of several parts. To collect metrics for Windows Server-related objects, import the Monitoring part for the operating systems that you plan to monitor: Microsoft.Windows.Server.<OperatingSystemVersion>.Monitoring

Adding Custom Metrics to the Collection Scope

The metric filter configuration file (MetricFilterConfig.xml) contains entries for the metric counters that are collected from the integrated Microsoft SCOM instance. These counters are selected in the Metrics page of the Configuration Utility. If the metrics that you intend to collect are not available with the bundled management packs, you can add them to the metric filter configuration file by directly editing it.

To add custom metrics to the metric collection scope, perform the following:

1. Back up the metric filter configuration file.

2. On the Operations Connector host, navigate to the <OvDataDir>\datafiles\HPBsmIntSCOM\<InstanceID> directory.

   The <InstanceID> string contains the version of the integrated Microsoft SCOM instance (and its consecutive number if it is not the first instance in a multiple instance configuration). Example value: SCOM2007_3.

3. Open the MetricFilterConfig.xml file in a plain text editor.

4. Modify the XML file and make sure to preserve the following format:

   <?xml version="1.0" encoding="UTF-8"?>
   <HPSCOMMetricConfig>
     <class name="[Name of Configuration Group 1]">
       <counter>[Counter 1 Name]/counter>
       <counter>[Counter 2 Name]</counter>
     </class>
     <class name="[Name of Configuration Group 2]">
       <counter>[Counter 3 Name]/counter>
       <counter>[Counter 4 Name]</counter>
     </class>
   
     ...
   
   </HPSCOMMetricConfig>

   For the [Name of Configuration Group N] and [Counter N Name] instances specify the actual values.

5. Save your changes.

6. Restart the metric integration service as described in Restarting the Services.

The metrics that you add by using the previous procedure are removed as soon as you reconfigure the metric collection scope from the Configuration Utility.

The following causes might keep a newly added metric from being propagated to OpsCx for Microsoft SCOM:

• The last collection happened after the time the metric was refreshed for the last time by Microsoft SCOM. In such a case, the metric does not appear in OMi until Microsoft SCOM refreshes the metric. This may take up to 12 hours, depending on the collection interval set in Microsoft SCOM.
• The rule for collecting the counter is not enabled in Microsoft SCOM. For instructions on how to enable monitoring rules or change their refresh times, see the Microsoft SCOM documentation.

Related topics

Modifying Operations Connector Policies

Configuring the Topology Integration

Configuring the Metric Integration

Backing up the Configuration