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

Configure a MID Server for Operational Metrics

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

Configure a MID Server for Operational Metrics

To use Operational Metrics, you need to configure at least one dedicated MID Server with ServiceAnalytics as a supported application, and with the ITOA Metrics capability. To ensure uninterrupted services, consider to also configure a failover MID Server cluster for Operational Metrics.

Before you begin

If Domain Support - Domain Extensions Installer is activated, then you can configure a dedicated MID Server with the ITOA metrics capability, per domain. In this case, metrics for a business service are processed on the MID Server that is in the same domain as the business service. Otherwise, a MID Server from the global domain is used.
Table 1. Hardware requirements (scaled for 2,500 CIs, with 20 metrics per CI)
Component Requirement
  • Minimum: 4 GB
  • Recommended: 8 GB
  • Minimum: Either of the following processors:
    • Core 2+
    • Xeon processor with a speed over 2 GHz
  • Recommended: Quad-core
Disk space
  • Minimum: 16 GB
  • Recommended: 24 GB
Table 2. Software requirements
Software Supported versions Additional requirements
Windows 32-bit and 64-bit versions:
  • Windows 2008 R2
  • Windows Server 2012 R2
32-bit version of the MID Server
  • Red Hat Enterprise Edition Linux 6.6 or later
  • CentOS Linux 6.6 or later
32-bit or 64-bit version of the MID Server
Table 3. Configuration requirements
Configuration Requirement
MID Server service logon user (required only for pulling) Must be set to a user with read access to the SCOM database (OperationsManagerDW).
  1. On the MID Server, open the MID Server Properties dialog box.
  2. Click the Log On tab.
  3. Select This account, and enter credentials for a user with the required access.
  4. Click Apply.

Role required: admin

About this task

The Operational Metrics MID Server supports the Operational Metrics feature by processing data and detecting anomalies. The statistical model is calculated on the Metric MID Server, which is then transmitted to the instance. Anomaly alerts are generated and scored on the Metric MID Server. The MID Server transmits batches of processed data to the instance every 15 minutes. If an anomaly is detected, then information about the anomaly along with the raw data is sent immediately to the instance, regardless of the regular 15-minute cycle.

By default, the MID Server is set up as a dedicated MID Server for Operational Metrics, and an attempt to add additional supported applications to the same MID Server is prevented. It is recommended that Service Analytics RCA is also implemented with its own dedicated RCA MID Server. These recommendations ensure high level of performance. However, if needed, you can modify this default behavior and configure the Operational Metrics MID Server or the RCA MID Server with additional supported applications. For information about modifying the behavior of the ALL option when selecting supported applications, see Configure applications included in ALL Applications .


  1. Ensure that the MID Server is validated.
    For more information, see Validate a MID Server.
  2. Navigate to MID Server > Servers.
  3. Click the MID Server that you want to configure as an Operational Metrics MID Server, or click New to create a new MID Server.
  4. Add the ServiceAnalytics application:
    1. At the center of the MID Server form, click Supported Applications.
    2. In the Supported Applications section click Edit.
    3. In the slushbucket select ServiceAnalytics and click the > add button.
    4. Click Save.
    If the MID Server needs to support ServiceAnalytics as well as one or more other applications, you can modify the definition of the ALL option to include these applications, and then select ALL in the slushbucket. ALL is the only option to which it is valid to add the ServiceAnalytics option. Performance might be compromised with these settings.
  5. Add the ITOA Metrics capability:
    1. At the center of the MID Server form, click Capabilities.
    2. In the Capabilities section click Edit.
    3. In the slushbucket select ITOA Metrics and click the '>' add button.
    4. Click Save.
  6. Click Update.

What to do next

Create a failover cluster for Operational Metrics. In this cluster, add the MID Servers that were configured for Operational Metrics. For more information, see MID Server cluster configuration.