Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

MID Servers and MID Server distributed clusters for Operational Intelligence

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

MID Servers and MID Server distributed clusters for Operational Intelligence

To use Operational Intelligence, create at least one MID Server distributed cluster which contains at least one MID Server configured for Operational Intelligence.

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.

Even if using a single 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. The first MID Server that is added to a distributed cluster, is designated as the Cluster Leader.

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

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

Configure a MID Server for Operational Intelligence

To use Operational Intelligence, you need to configure at least one MID Server with OperationalIntelligence as a supported application, with the Metrics capability, and which runs the Operational Intelligence Metrics extension. Then, add that Operational Intelligence MID Server as a member to a MID Server distributed cluster.

Before you begin

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.

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

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
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.
Update the wrapper-override.xml file in folder ../agent/conf:
// These properties set the memory for Java virtual machine.
// With these properties, the MID Server is set up to use up to 8 GB of memory. By default, the server will start with 4GB of memory.
wrapper.java.maxmemory=8192
wrapper.java.initmemory=4096

// These properties are related to java garbage collection
wrapper.java.additional.5=-XX:+UseParNewGC
wrapper.java.additional.6=-XX:+UseConcMarkSweepGC
wrapper.java.additional.7=-XX:+UseTLAB
wrapper.java.additional.8=-XX:NewSize=128m
wrapper.java.additional.9=-XX:MaxNewSize=128m
wrapper.java.additional.10=-XX:MaxTenuringThreshold=0
wrapper.java.additional.11=-XX:SurvivorRatio=1024
wrapper.java.additional.12=-XX:+UseCMSInitiatingOccupancyOnly
wrapper.java.additional.13=-XX:CMSInitiatingOccupancyFraction=40
wrapper.java.additional.14=-XX:MaxGCPauseMillis=1000
wrapper.java.additional.15=-XX:InitiatingHeapOccupancyPercent=50
wrapper.java.additional.16=-XX:+UseCompressedOops
wrapper.java.additional.17=-XX:ParallelGCThreads=8
wrapper.java.additional.18=-XX:ConcGCThreads=8
wrapper.java.additional.19=-XX:+DisableExplicitGC

Role required: To access the MID Server - mid_server. To configure a MID Server in an instance (for example, to add a supported application), refer to the MID Server documentation.

About this task

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.

The Operational Intelligence MID Server is configured with the OperationalIntelligence application which allows you to 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.

Procedure

  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 Intelligence MID Server, or click New to create a new MID Server.
  4. Add the OperationalIntelligence 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 OperationalIntelligence and click the > add button.
    4. Click Save.
  5. Add the 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 Metrics and click the '>' add button.
    4. Click Save.
  6. Click Update.

What to do next

Create a MID Server distributed cluster, and add the Operational Intelligence MID Server as a member to that cluster.

Create a MID Server distributed cluster for Operational Intelligence

After creating at least one MID Server for Operational Intelligence, you must create a MID Server distributed cluster for Operational Intelligence. To this cluster, add any MID Servers that are configured for Operational Intelligence. At least one Operational Intelligence MID Server must be included in this cluster.

Before you begin

Role required: evt_mgmt_admin or agent_admin can manage cluster records

About this task

Operational Intelligence uses two ports on each MID Server distributed cluster:
  • One port for Discovery
  • One port for communications

When deploying multiple Operational Intelligence MID Servers on the same physical server, allocate two ports for each additional MID Server. If for example, you deploy two Operational Intelligence MID Servers on the same physical server, then four ports are required.

Procedure

  1. Navigate to MID Server > Clusters.
  2. Click New.
  3. Fill out the MID Server Cluster form.
    Field Description
    Name Name of the cluster.
    Type Cluster type which must be set to Distributed.
  4. Right-click the form banner and select Save.
  5. Additional fields appear on the MID Server Cluster form. Review the details, and then click Update if you modified any fields.
    Field Description
    Distributed Cluster Indicates that the cluster type is distributed.
    Status The cumulative status of the cluster, which can be Started, Stopped, Error, or Warning.
    Error Message The most recent error message that was generated for the cluster.
    Port Starting port in the port range to use for communication with other Operational intelligence MID Servers in the distributed cluster.

    Default value is 47100.

    Note: If the same virtual machine/host server runs multiple Operational Intelligence MID Servers, and if those MID Servers are communicating with different ServiceNow instances or are part of a different distributed cluster on the same ServiceNow instance, then use separate ports for each cluster.
    Port count The number of ports to use for communication with other Operational intelligence MID Servers in the MID Server distributed cluster.

    Port count is used with Port to determine a range of ports. If the value of Port is 47100, and the value of Port count is four, the ports 47100- 47103 are used for communication.

    Default value is four. Do not modify this value if only a single MID Server is configured on a physical server. Otherwise, increase this value by two for each additional MID Server that is implemented on a single physical server.

  6. In the Includes MID Servers related list, click Edit to add MID Servers to the cluster.
  7. Use the slushbucket to add only MID Servers that were configured for Operational Intelligence. Then click Save.
  8. On the MID Server Cluster form, click Update.
    Note: The Operational Intelligence MID Servers do not join the distributed cluster until you configure the Operational Intelligence extension, which is the next step in setting up Operational Intelligence.

Parameters of MID Server distributed cluster

The following MID Server parameters support the MID Server Distributed cluster type.

You can access these parameters in the Configuration Parameters related list of a MID Server. To add and set any of these parameter, see Add a MID Server parameter.

Parameter Description
mid.distributed.cluster.striped.threadpool.size Size of striped threadpool in MID Server distributed cluster.
  • Type: integer
  • Default value: Number of cores on the virtual machine or server.
mid.distributed.cluster.log.level

Logging level for MID Server distributed cluster, which can help troubleshooting. However, logging impacts the performance of Operational Intelligence.

An empty value designates no logging.

  • Type: integer
  • Default value: none
  • Other possible values: info, debug, trace
mid.distributed.cluster.global.timeout Global timeout in seconds for MID Server distributed cluster.
  • Type: integer
  • Default value: 180
  • Other possible values:
    • Minimum value: 60 (not enforced)
    • Maximum value: 300 (not enforced)
mid.distributed.cluster.node.max.off.heap.memory The amount of off heap memory used by Operational Intelligence to process data series per minute.

The default 4 GB of space is the amount of off heap memory needed for processing 800,000 data series per minute. Adjust this value proportionally to the amount of actual data series. For example, to process 400,000 data series per minute, you can change the value to 2048.

  • Type: integer
  • Default value: 4096

Scheduled jobs included with MID Server distributed cluster

The following MID Server scheduled job is included with the MID Server Distributed cluster type.

Name Description
Validate MID distributed cluster Validates status of the cluster node for each MID Server in the cluster. For a MID Server that is down and its status is not stopped, updates the node status to stopped.

Also, validates overall status of the cluster. During this validation, the job stops the cluster if there are multiple sub-clusters in a single cluster.

Feedback