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

MID Server and MID Server distributed cluster for Operational Intelligence

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

MID Server and MID Server distributed cluster for Operational Intelligence

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

Even if using a single Operational Intelligence MID Server, that server must be added to a MID Server distributed cluster, and any additional MID Servers in that cluster, must be configured for Operational Intelligence. All Operational Intelligence MID Servers must be members of a MID Server distributed cluster. The first MID Server that is added to a distributed cluster, is designated as the Cluster Leader.

To support the specified throughput, create a distributed cluster with a single MID Server that meets the Operational Intelligence MID Server requirements. To support high availability, create a distributed cluster with two such MID Servers.

See Get started with Operational Intelligence for the high level steps of setting up Operational Intelligence.

MID Server distributed clusters

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

In a distributed cluster type, the MID Servers in the cluster communicate with each other to distribute and balance the work load. This communication requires that all MID Servers in a distributed cluster are able to communicate with each other. Ensure that the specified ports are open and that there are no firewalls that block communication.

Operational Intelligence MID Server

The Operational Intelligence MID Server supports the Operational 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, regardless of the regular 10-minute cycle.

Each Operational Intelligence MID Server must be configured with the following settings:
  • OperationalIntelligence as a supported application
  • the Metrics capability
  • running the Operational Intelligence Metrics extension

The OperationalIntelligence application that the Operational Intelligence MID Server is configured with, lets you add additional supported applications to the same MID Server. By default, Operational 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 Operational 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)
Component Requirement
Memory
  • Minimum: 12 GB
Processor
  • Minimum: 8 cores
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 2016
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.

Configuration Override

Update the wrapper-override.conf file in folder ../agent/conf:
  • Add the following code at the bottom of the file:
     
    # GC
    wrapper.java.additional.5=-XX:+AlwaysPreTouch
    wrapper.java.additional.6=-XX:+UseG1GC
    wrapper.java.additional.7=-XX:+ScavengeBeforeFullGC
    wrapper.java.additional.8=-XX:+DisableExplicitGC
     
    # IP4
    wrapper.java.additional.9=-DpreferIPv4Stack=true
  • Optionally, if a server has additional RAM available, for example 16 GB RAM, you can replace 4096 with 8192 in: wrapper.java.maxmemory=4096.
Feedback