Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Get started with Operational Metrics

Log in to subscribe to topics and get notified when content changes.

Get started with Operational Metrics

Complete the following setup and initial configuration steps to start using Operational Metrics.

About this task

Raw metric data, collected by data sources (such as SCOM) needs to reach the Operational Metrics MID Server, where Operational Metrics can process and analyze it. You can set up Operational Metrics so that raw data is either pulled by the Operational Metrics MID Server from the external data source, or pushed from the external data source to the Operational Metrics MID Server.

Using either method requires the configuration of the ITOA MetricExtension MID Server extension. The main roles of this extension are to normalize the raw data, and to detect any anomalies. The normalized data and anomalies (if above the specified threshold), are then transmitted to the instance.

Some steps for setting up Operational Metrics must be completed regardless of the method used. Other steps depend on the method used for transmitting data between the data source and the MID Server:


This method requires using a connector that is configured to pull data from the specific data source that is collecting the raw data. Use the pre-defined SCOM connector (which was previously defined for pulling events from SCOM), or configure a new custom connector specifically for the external source that is used in your environment.


This method uses web service APIs and is based on client-side tools that push the raw data from the external source to the MID Server. This method requires that the ITOA MetricExtension extension is configured with the Enable REST Listener option enabled.

You also need to configure the Web Server extension, which starts a Web Server on the MID Server. Request handlers are added on the Web Server that listen to any incoming metric data that was pushed from the external source. The configuration of the Web Server extension includes two important settings:
  • Authentication type, which can be set to the more advanced option - Keybased.
  • Secure Connection, which lets you choose whether incoming and outgoing data is secured when transmitted. If you choose the more advanced secured option, it requires that you obtain a certificate from a well known certificate authority, and then provide the Keystore Certificate Alias and the Keystore Password.


  1. Activate the ITOM Metric Management plugin.
  2. Configure a MID Server for Operational Metrics: Set up the MID Server with the required hardware and with the ITOM Metric capability from ITOM Metric Management. It is possible to use the same MID Server that is being used for Service Analytics, as a dedicated MID Server for Service Analytics and Operational Metrics. If the default SCOM connector is used, then the same MID Server that is used to collect events, should be used for Operational Metrics.
  3. Configure the Operational Metric extension.
  4. To configure for pulling:
    1. Create a connector definition (For a SCOM connector - this is already defined for pulling events from SCOM).
    2. Configure a connector instance (For a SCOM connector - see Configure the SCOM connector instance).
  5. To configure for pushing:
    1. Configure the MID Web Server extension.
    2. In the ITOA MetricExtension extension, ensure that the Enable REST Listener option is enabled, and that the MID Web Server Extension is set.
    3. Create the client scripts that push the raw data from the external source to the MID Server.
  6. Create or configure metric type registration.
  7. Choose and configure metrics to monitor.
  8. Create event rules to map raw data to specific CI types to bind metrics to CIs.