Qumulo

Application Version and Upgrade Details

Introduction

Qumulo Core is a high-performance file data platform designed to store, manage and create workflows and applications with data in its native file form at a massive scale across hybrid cloud environments. With Qumulo you can easily manage the full data lifecycle from ingestion, transformation, publishing and archiving with cost-effective capacity, dynamic scalability, automatic encryption, real-time analytics and an advanced API that enables customers to easily integrate Qumulo into their technology ecosystem and workflows.

Key Use cases

Discovery Use cases

• It discovers the Qumulo components.
• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

• Provides metrics related to job scheduling time and status etc..
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource

Prerequisites

• Classic gateway version should be 14.0.0 and above.
• Nextgen gateway version should be 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

Hierarchy of Qumulo

          · Qumulo Cluster
                  · Qumulo Node
                        · Qumulo Cluster Disk
                  · Qumulo Quota
                  · Qumulo SMB Share
                  · Qumulo NFS Export

Supported Metrics

Default Monitoring Configurations

Qumulo has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of Qumulo. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: qumulo Qumulo Cluster - 1 (i.e, appName = qumulo , nativeType = Qumulo Cluster , version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of Qumulo. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: qumulo Qumulo Cluster Template - 1 (i.e, appName = qumulo , nativeType = Qumulo Cluster, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: Qumulo Cluster Monitor qumulo Qumulo Cluster 1(i.e, monitorKey = Qumulo Cluster Monitor , appName = qumulo, nativeType = Qumulo Cluster , version = 1)

Configure and Install the Qumulo Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed. Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the Qumulo application.
   Note: Select the version from the drop down menu.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned Basic Information:

Notes

• By default the Is Secure checkbox is selected.
• Host Name/IP Address and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

9. Select the below mentioned Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:

    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.

11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector by providing a name or use the pre-populated name.

16. Select an existing registered profile.

17. Click FINISH.

The application is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the Qumulo application.

View the Qumulo Details

To discover resources for Qumulo.

1. Navigate to Infrastructure > Search > Servers and VMs > Qumulo.
2. The Qumulo page is displayed, select the application name.
3. The RESOURCE page appears from the right.
4. Click the ellipsis (…) on the top right and select View details.
5. Navigate to the Attributes tab to view the discovery details.

6. Click the Metrics 2.0 tab to view the metric details for Qumulo.

Resource Filter Input keys

Qumulo Resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alerts based on customisation.

Supported macros keys:

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables “App Failure Notifications” in configuration.
  • Connectivity Exception
  • Authentication Exception
• Application will send any duplicate/repeat failure alert notification for every 6 hours.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts.
• This application supports only Classic Gateway and NextGen Gateway. Not supported with Cluster Gateway.
• Component level thresholds can be configured on each resource level.
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• Latest snapshot metric support from Gateway 14.0.0.