Enabling Cloud-Based Monitoring for Qumulo Core

This section explains how to enable Cloud-Based Monitoring for your Qumulo cluster.

How Cloud-Based Monitoring Works

Cloud-Based Monitoring (which includes Nexus Monitoring functionality) sends telemetry data to Qumulo to allow the Qumulo Care team to monitor your Qumulo cluster proactively.

Important
Cloud-Based Monitoring and Nexus Monitoring don’t collect file names, path names, client IP addresses, or account credentials.

We use a proprietary application that aggregates diagnostic cluster data and alerts the Qumulo Care team if an issue arises. Depending on the issue severity and cluster state, a member of the Qumulo Care team reaches out. For more information, see:

What Data Gets Sent to Qumulo

Cloud-Based Monitoring lets your cluster send the following detailed diagnostic data to Qumulo through an encrypted connection.

Cluster name
Number of nodes in cluster
Hardware and software incidents
- Drives
  - CRC errors
  - S.M.A.R.T. status alerts
  - Capacity triggers
- Nodes
  - PSU failure
  - Fan failure
  - Recused node
  - Offline node
  - Unreachable cluster
- Qumulo Core
  - New process core dump
Configuration data (such as users, groups, SMB shares, and NFS exports)
Logs, stack traces, and code dumps

Prerequisites

Before you can use Cloud-Based Monitoring, you must enable the following destination hostnames for TCP on port 443:

Hostname	Description
`api.missionq.qumulo.com`	Cloud-Based Monitoring connectivity
`monitor.qumulo.com`	Cloud-Based Monitoring log uploads
`api.nexus.qumulo.com`	Nexus Monitoring connectivity