This section explains how Qumulo Alerts monitors alarms and alerts for a Qumulo Core Cluster.

How Qumulo Alerts Works

Qumulo Alerts is a Docker-based system that comprises multiple containers. The main container uses a series of plugins to collect hardware alarms and software alerts from Qumulo Core clusters.

In Qumulo Alerts, producers are Docker containers that take data from various sources, pass it through the Exchange, a processing queue, and finally give it to consumers, defined users or user groups. Aside from processing data, the Exchange facilitates the transfers between the producers and consumers.

Qumulo Alerts Architecture Diagram

Both producers and consumers use plugins that help process alarms and alerts from a Qumulo Core cluster. A plugin is a mechanism that processes a single function, such as fan failure, disk failure, or node failure. Plugins help with granular control over the information that Qumulo Alerts collects and processes.

Known Limitations of Qumulo Alerts

This section lists the currenly known limitations for Qumulo Alerts.

  • Floating IP Addresses or Network Load Balancing (NLB): To prevent overloading any node in a Qumulo cluster, Qumulo Alerts plugins connect to all nodes in the cluster by using floating IP addresses or an NLB.

  • Error Logging: Qumulo Alerts generates a large number of error messages that can help you debug issues. However, currently, all logging remains within the Docker container and is therefore not accessible easily. For help with troubleshooting issues, contact the Qumulo Care team.

  • Connectivity to the Cluster: If Qumulo Alerts loses connectivity to your Qumulo cluster for more than 10 minutes, you can start a new Qumulo Alerts session or contact the Qumulo Care team for help with debugging your running session. This scenario might occur when there is a VPN that requires re-authentication.

  • JSON-Based Configuration: Currently, to configure Qumulo Alerts, an administrator must edit multiple JSON files.