MID Server distributed cluster for Metric Intelligence

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of MID Server distributed cluster for Metric Intelligence

    To use Metric Intelligence in ServiceNow, you must have at least one MID Server distributed cluster containing a MID Server configured specifically for Metric Intelligence. A single Metric Intelligence MID Server must be part of such a distributed cluster to support the required throughput. Only one Metric Intelligence MID Server can run on a virtual machine. MID Servers configured for Metric Intelligence can also connect to multiple Agent Client Collectors (ACC-M and ACC-L) and can support other applications such as Discovery.

    Show full answer Show less

    Activating the Metric Intelligence application automatically activates the MID Server distributed cluster plugin, which is dedicated to Metric Intelligence. If automatic cluster creation fails, manual configuration with Customer Support assistance is possible.

    Metric Intelligence MID Server Configuration

    The Metric Intelligence MID Server processes metrics data and detects anomalies, sending both processed data batches and anomaly alerts to the ServiceNow instance.

    Key configuration requirements for the Metric Intelligence MID Server include:

    • Supporting the Metric Intelligence application and Metrics capability.
    • Running the Metric Intelligence Metrics extension.
    • IPv6 is not supported; only IPv4 is supported.
    • By default, Metric Intelligence is included in the MID Server’s ALL supported applications option, which can be customized.
    • If Domain Support - Domain Extensions Installer is enabled, MID Servers can be configured per domain to process metrics for business services within the same domain.
    • The MID Server must be validated, active, and meet all software, hardware, and configuration prerequisites.

    Hardware and Software Requirements

    Hardware specifications depend on scale:

    • A MID Server with 12 GB RAM and 4 cores can support up to 1.2 million metrics (12,000 CIs with 100 metrics each).
    • A MID Server with 24 GB RAM and 8 cores can support up to 1.7 million metrics (17,000 CIs with 100 metrics each).

    Supported operating systems include:

    • Windows Server versions from 2008 R2 to 2025 (32-bit and 64-bit).
    • Linux distributions such as Red Hat Enterprise Linux 6.6 or later and CentOS Linux 6.6 or later (32-bit and 64-bit).

    Configuration Requirements

    • MID Server service logon user: Must have read access to the SCOM database (OperationsManagerDW) when pulling data.
    • Throttling mechanism: Enabled by default to prevent data bursts from overloading the instance, ensuring no data loss. Can be disabled temporarily for troubleshooting via configuration parameters on the MID Server record.
    • Java and memory configuration: Java override parameters such as garbage collector type and IPv4 preference can be set in the wrapper-override.conf file.
    • Memory settings: Configured in the wrapper.conf file, with recommended initial memory at least 1024 MB and max memory at least 4096 MB. Higher memory allocation (e.g., 8192 MB) is possible if the server has sufficient RAM.

    Practical Implications for ServiceNow Customers

    Setting up and configuring a MID Server distributed cluster for Metric Intelligence ensures efficient metric data processing and anomaly detection at scale. Understanding the hardware, software, and configuration prerequisites helps customers optimize MID Server performance and stability. The throttling mechanism protects the ServiceNow instance from overload during high data throughput, while Java and memory tuning enable better MID Server resource utilization. Proper domain configuration supports multi-domain environments by assigning metric processing to the appropriate MID Server.

    Using Metric Intelligence requires at least one MID Server distributed cluster which contains a single MID Server that is configured for Metric Intelligence.

    When using a single Metric Intelligence MID Server, that server must be added to a MID Server distributed cluster.

    To support the specified throughput, create a distributed cluster with a single MID Server that meets the Metric Intelligence MID Server requirements. When using a virtual machine (VM), only a single MID Server can run that supports Metric Intelligence. When working with Agent Client Collector, a MID Server can also be connected to multiple agents (ACC-M and ACC-L).

    A MID Server supporting Discovery can also be used with other applications.

    For details on setting up Metric Intelligence, see Get started with Metric Intelligence.

    MID Server distributed clusters

    Activating Metric Intelligence (com.snc.sa.metric), automatically activates MID Server distributed cluster (com.snc.agent.distributed.cluster). A MID Server distributed cluster supports the Distributed MID Server cluster type which is used exclusively with Metric Intelligence.

    If automatic creation of a MID Server distributed cluster fails, you can configure the cluster manually. For details, contact Customer Support.

    Metric Intelligence MID Server

    The Metric Intelligence MID Server supports the Metric Intelligence feature by processing data and detecting anomalies. The MID Server transmits batches of processed data to the instance. If an anomaly is detected, then information about the anomaly along with the raw data is sent immediately to the instance.

    Each Metric Intelligence MID Server must be configured with the following settings:
    • Metric Intelligence as a supported application
    • The Metrics capability
    • Running the Metric Intelligence Metrics extension
    Note:
    The Metric Intelligence MID Server does not support IPv6.

    The Metric Intelligence application that the Metric Intelligence MID Server is configured with enables you to add additional supported applications to the same MID Server. By default, Metric Intelligence is included in the definition of the MID Server ALL option. For information about modifying the behavior of the ALL option when selecting supported applications, see Configure applications included in ALL Applications.

    If Domain Support - Domain Extensions Installer is activated, then you can configure a MID Server with the 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.

    Ensure that the MID Server that you want to configure for Metric Intelligence:
    • Is validated. For more information, see Validate a MID Server
    • Is in running state
    • Meets all software, hardware, and configuration requirements
    Table 1. Hardware requirements for the virtual machine/host on which the MID Server runs (scaled for 5000 CIs with 100 metrics per CI)
    Requirement
    One MID Server with:
    • Memory: 12 GB
    • Processor: 4 cores
    		 Supports approximately up to a total of 1.2 million metrics (12,000 CIs with 100 metrics per CI).
    One MID Server with:
    • Memory: 24 GB
    • Processor: 8 cores
    		 Supports approximately up to a total of 1.7 million metrics (17,000 CIs with 100 metrics per CI).
    Table 2. Software requirements
    Software Supported versions Additional requirements
    Windows 32-bit and 64-bit versions:
    • Windows 2008 R2
    • Windows Server 2012 R2
    • Windows Server 2019
    • Windows Server 2022
    • Windows Server 2025
    		 32-bit or 64-bit version of the MID Server
    Linux
    • 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.

    MID Server throttling mechanism

    The MID Server throttling mechanism protects against data bursts to the instance. Data burst protection prevents overloading the instance, while ensuring that you do not lose any data.

    The MID Server throttling mechanism is enabled by default. You may want to disable this mechanism when troubleshooting, to ensure that the mechanism is not causing system malfunction.

    The throttling parameters are MID Server configuration parameters. Configure these parameters on the MID Server record, on the Configuration Parameters tab. When you add a configuration parameter, select the matching mid.oi parameter from the Parameter name list.

    • To disable this feature for metrics, set the mid.oi.metric_token_bucket_enabled parameter to false.
    • To disable this feature for anomalies, set the mid.oi.anomaly_token_bucket_enabled parameter to false.

    Configuration Override

    Use the ../agent/conf/wrapper-override.conf file to configure Java override parameters, such as the garbage collector and IPv4.

    To configure the garbage collector, override the existing garbage collector parameter. For example, replace -XX:+UseParallelGC with -XX:+UseG1GC.

    To force IPv4, add the following parameter, using the next available wrapper.java.additional number:

    wrapper.java.additional.<number>=-Djava.net.preferIPv4Stack=true
    Note:
    Do not renumber existing wrapper.java.additional lines. Parameters 101 through 200 are reserved for ServiceNow out-of-the-box parameters. Only override those parameters by uncommenting the existing lines and changing the values.

    Use the ../agent/conf/wrapper.conf file to configure memory for Metric Intelligence. Update the following parameters:

    • wrapper.java.initmemory=1024 or higher
    • wrapper.java.maxmemory=4096 or higher

    Optionally, if a server has additional RAM available, for example 16 GB RAM, you can replace 4096 with 8192 in wrapper.java.maxmemory=4096.