Qumulo's Cloud-Based Monitoring

IN THIS ARTICLE

Outlines the configuration and support for Cloud-based Monitoring.

REQUIREMENTS

• Cluster running Qumulo Core
• Protocols/ports allowed to the following destination hostnames as outlined in the table below:

DETAILS

Cloud-Based Monitoring is an internal monitoring tool that allows Qumulo’s Customer Success team to proactively monitor your cluster. Enabling this feature in the UI or via the qq CLI allows the cluster to send detailed diagnostic data over an encrypted connection to a Qumulo cloud instance. Qumulo has developed a proprietary application that aggregates cluster diagnostic data and sends alerts to our Customer Success team should an issue arise.

Once enabled, the following data will be collected by Qumulo so that our team can proactively reach out if an incident occurs.

• Cluster name and number of nodes
• Performance and capacity statistics
• Notification of hardware and software issues
• Configuration data including users, groups, shares and exports
• Logs, stack traces, and core dumps

Note: The Cloud-Based Monitoring service does not collect file & path names, client IP addresses, and login information (such as usernames & passwords).

ENABLE AND DISABLE CLOUD-BASED MONITORING

Qumulo Core Web UI

1. Hover over the Support menu and click Qumulo Care.
   
   
   
   
2. Click the Edit button for Cloud-Based Monitoring.
   
   
   
   
3. Enable Cloud-based Monitoring by selecting Yes or disable by selecting No.
   
   
   
   
4. Click Save.

Once enabled, Cloud-Based Monitoring will display as Connected on the Qumulo Care page:

QQ CLI

To enable Cloud-Based Monitoring via the qq CLI, run the following command from a node:

qq set_monitoring_conf --enabled

Run the command below to disable Cloud-Based Monitoring:

qq set_monitoring_conf --disabled 

Lastly, verify the cluster's monitoring configuration by using the following command:

qq monitoring_conf

PROACTIVE SUPPORT

With Cloud-Based Monitoring enabled, our team receives alerts 24/7 for the following incidents so that we can be available for help when you need it the most:

• Drive CRC errors & SMART status alerts
• Drive Failures (SSD & HDD)
• Capacity Triggers
• Power Supply Failure
• Fan failure
• New Process Core Dump
• Recused Node
• Node Offline
• Lost Communication with Cluster

Depending on the severity of the issue and the current state of the cluster, a member from our team will reach out in the following ways. Primarily, your team will be notified via Slack or email for most incidents listed above. For critical alerts, our team will call the phone number provided for the technical contact to resolve the issue. Reference Qumulo's SLA agreement below for additional details on expected response times.

We highly recommend that you enable Remote Support with Cloud-Based Monitoring so that our team can provide fast support during critical issues. Reference Qumulo's Remote Support article for additional details.

TIP! Enable email alerts in Qumulo Trends to receive notifications of cluster events including upgrades, quorum events or drive loss. To receive alerts and proactively monitor your cluster, reference the Email Alerting with Qumulo Trends article for information on enabling this feature.

RESOLUTION

You should now be able to utilize Qumulo's Cloud-Based Monitoring.

ADDITIONAL RESOURCES

Qumulo's Remote Support

Cloud-Based Monitoring via Custom Proxy

Qumulo Care Proactive Monitoring

QQ CLI: Monitoring and VPN

Like what you see? Share this article with your network!