Contents Now Platform Capabilities Previous Topic Next Topic Configure a dedicated MID Server for Service Analytics Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Configure a dedicated MID Server for Service Analytics To activate root cause analysis (RCA) with Service Analytics, configure at least one dedicated MID Server with analytics. To ensure uninterrupted services, it is recommended that you also configure a failover MID Server cluster for analytics. Before you beginIf the Domain Support - Domain Extensions Installer plugin is activated, then you can configure a dedicated MID Server with analytics, 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 Memory Minimum: 4 GB Recommended: 8 GB Processor 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: 32-bit version of the MID Server 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013, which you can download at http://www.microsoft.com/en-us/download/details.aspx?id=40784. 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 Role required: admin About this task The analytics MID Server supports the RCA process by hosting the RCA Learner and the real-time RCA query handler. On the analytics MID Server, the system builds models that support responses to root cause queries. The learner data on the analytics MID Server persists by default for a maximum of 90 days. The MID Server must be dedicated for Service Analytics, and an attempt to use it for Discovery for example, is prevented. Procedure Ensure that the MID Server is validated. For more information, see Validate a MID Server. Navigate to MID Server > Capabilities, and click Analytics. Select the MID Server that you want to configure analytics on. In the MID Servers section, click Edit. On the Edit Members form, select the MID Server and move it to the Analytics list. Click Save. Click Update. ResultThe Analytics MID Server is automatically configured with a Discovery IP range set to 0.0.0.0-0.0.0.0. What to do next Create a failover cluster for analytics. In this cluster, add the MID Servers that were configured for analytics. For more information, see Configure a MID Server cluster. Related ConceptsRoot cause CIs On this page Send Feedback Previous Topic Next Topic
Configure a dedicated MID Server for Service Analytics To activate root cause analysis (RCA) with Service Analytics, configure at least one dedicated MID Server with analytics. To ensure uninterrupted services, it is recommended that you also configure a failover MID Server cluster for analytics. Before you beginIf the Domain Support - Domain Extensions Installer plugin is activated, then you can configure a dedicated MID Server with analytics, 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 Memory Minimum: 4 GB Recommended: 8 GB Processor 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: 32-bit version of the MID Server 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013, which you can download at http://www.microsoft.com/en-us/download/details.aspx?id=40784. 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 Role required: admin About this task The analytics MID Server supports the RCA process by hosting the RCA Learner and the real-time RCA query handler. On the analytics MID Server, the system builds models that support responses to root cause queries. The learner data on the analytics MID Server persists by default for a maximum of 90 days. The MID Server must be dedicated for Service Analytics, and an attempt to use it for Discovery for example, is prevented. Procedure Ensure that the MID Server is validated. For more information, see Validate a MID Server. Navigate to MID Server > Capabilities, and click Analytics. Select the MID Server that you want to configure analytics on. In the MID Servers section, click Edit. On the Edit Members form, select the MID Server and move it to the Analytics list. Click Save. Click Update. ResultThe Analytics MID Server is automatically configured with a Discovery IP range set to 0.0.0.0-0.0.0.0. What to do next Create a failover cluster for analytics. In this cluster, add the MID Servers that were configured for analytics. For more information, see Configure a MID Server cluster. Related ConceptsRoot cause CIs
Configure a dedicated MID Server for Service Analytics To activate root cause analysis (RCA) with Service Analytics, configure at least one dedicated MID Server with analytics. To ensure uninterrupted services, it is recommended that you also configure a failover MID Server cluster for analytics. Before you beginIf the Domain Support - Domain Extensions Installer plugin is activated, then you can configure a dedicated MID Server with analytics, 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 Memory Minimum: 4 GB Recommended: 8 GB Processor 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: 32-bit version of the MID Server 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013, which you can download at http://www.microsoft.com/en-us/download/details.aspx?id=40784. 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 Role required: admin About this task The analytics MID Server supports the RCA process by hosting the RCA Learner and the real-time RCA query handler. On the analytics MID Server, the system builds models that support responses to root cause queries. The learner data on the analytics MID Server persists by default for a maximum of 90 days. The MID Server must be dedicated for Service Analytics, and an attempt to use it for Discovery for example, is prevented. Procedure Ensure that the MID Server is validated. For more information, see Validate a MID Server. Navigate to MID Server > Capabilities, and click Analytics. Select the MID Server that you want to configure analytics on. In the MID Servers section, click Edit. On the Edit Members form, select the MID Server and move it to the Analytics list. Click Save. Click Update. ResultThe Analytics MID Server is automatically configured with a Discovery IP range set to 0.0.0.0-0.0.0.0. What to do next Create a failover cluster for analytics. In this cluster, add the MID Servers that were configured for analytics. For more information, see Configure a MID Server cluster. Related ConceptsRoot cause CIs
