Moogsoft Docs

High Availability Overview

Moogsoft AIOps supports high availability (HA) architectures to make the system more fault tolerant. Each component supports a multi-node architecture to enable redundancy, failover, or both to minimize risk of data loss. For example, in the case of a hardware failure.

This topic covers the architectures you can use for to achieve HA with Moogsoft AIOps . For an example of how to set up a single site HA system, see Single Site High Availability. See High Availability Reference Architecture for detailed diagram of the components in a single site HA configuration.

HA Architecture Basics

In its simplest form, each Moogsoft AIOps cluster runs on a designated host and the two hosts constitute an HA pair. The third party components Elasticsearch, RabbitMQ, and the database require an additional node to achieve HA. The following diagram illustrates a single site scenario for HA using two full stacks of Moogsoft AIOps, a primary cluster and a secondary cluster:

ha.png

Distributed HA Architectures

Moogsoft AIOps supports high availability in distributed architectures where different machines host a subset of the stack. The dotted lines in the diagram illustrate one to divide clusters into a distributed architecture. For example you can separate the UI stack (A) from the database (B) and the database from the remaining layers (C). Alternatively, you can run LAMs for data ingestion on separate hosts.

When choosing how to distribute the components of your HA deployment onto multiple hosts, you must run the following components on the same host:

  • The UI stack (Nginx and Tomcat) .

  • Data processing (Moogfarmd), the message bus (RabbitMQ), and search (Elasticsearch).

The database and LAMs can run on hosts with no other components. However, to minimize latency between Moogfarmd and the database, it is a good idea to run both components on the same host. If you choose to run the database separately from Moogfarmd, there should be no more than 5 ms latency between components.

To increase capacity within the HA architecture, you can:

  • Add memory or CPU to hosts running Moogfarmd. If you add additional machines beyond a single HA pair, you increase redundancy but not capacity.

  • Add hosts to increase LAM processing capacity. If you implement this model, do not extend the LAM capacity beyond the capacity of Moogfarmd to process incoming events and alerts.

See Sizing Recommendations for more information on hardware sizes and capacity.

After you decide on the best HA architecture for your environment, you can plan your implementation.