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

Configure a MID Server for Service Analytics RCA

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

Configure a MID Server for Service Analytics RCA

To activate the Service Analytics root cause analysis (RCA) feature, configure at least one dedicated MID Server with the ServiceAnalytics as a supported application, and with the RCA capability. To ensure uninterrupted services, it is recommended that you also configure a failover MID Server cluster for RCA.

Before you begin

If the Domain Support - Domain Extensions Installer plugin is activated, then you can configure a dedicated MID Server with the RCA capability, per domain. In this case, RCA for a business service is done 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
Component Requirement
  • Minimum: 4 GB
  • Recommended: 8 GB
  • Minimum: Either of the following:
    • Core 2+
    • Xeon processor with a speed over 2 GHz
  • Recommended: Quad-core
Disk space (for 100 discovered services)
  • Minimum: 8 GB
  • Recommended: 10 GB
Table 2. Software requirements
OS Supported OS versions Additional requirements
Windows 32-bit and 64-bit versions:
  • Windows 2008 R2
  • Windows Server 2012 R2
For either version of the OS:
  • 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

Role required: admin

About this task

The RCA MID Server supports the Service Analytics RCA process by hosting the RCA Learner and the real-time RCA query handler. On the RCA MID Server, the system builds models that support responses to root cause queries. The learner data on the RCA MID Server persists by default for a maximum of 90 days.

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


  1. Ensure that the MID Server is validated.
    For more information, see Validate the MID Server.
  2. Navigate to MID Server > Servers.
  3. Double-click the MID Server that you want to configure as an RCA 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 RCA capability:
    1. At the center of the MID Server form, click Capabilities.
    2. In the Capabilities section click Edit.
    3. In the slushbucket select RCA and click the '>' add button.
    4. click Save.
  6. Click Update.


The RCA MID Server is automatically configured with a Discovery IP range set to

What to do next

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