Supported Versions
Rubrik cluster software version: 8.0.2-p2-22662


Rubrik simplifies backup and recovery for hybrid cloud environments. By combining data orchestration, catalog management, and deduplicated storage into a singular software platform, it removes the complexity of legacy backup systems. Enterprises can use Rubrik’s API-first software tool to automate automation and unlock cloud for long-term data retention or disaster recovery. Rubrik supports the top operating systems, databases, hypervisors, clouds, and SaaS apps and was made to be vendor-neutral.

Rubrik assists organizations in maintaining data integrity, provides data availability that withstands challenging circumstances, constantly tracks data risks and threats, and restores businesses with their data when infrastructure is attacked.

Key Use cases

Discovery Use cases

  • It discovers the Rubrik Cluster 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,.
  • Generates alerts for each metric and notifies administrators about the issue with the resource.


  • OpsRamp Classic Gateway 13.0.0 and above.
  • Provided IpAddress/hostname, credentials should work for Rubrik REST API’s.

Hierarchy of Rubrik resources

  - Rubrik Cluster
         - Rubrik Node
                    - Rubrik Disk

Default Monitoring Configurations

Rubrik has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

  1. Default Global Device Management Policies

    OpsRamp has a Global Device Management Policy for each Native Type of Rubrik Cluster. 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: rubrik Rubrik Cluster - 1 (i.e, appName = rubrik, nativeType =Rubrik Cluster, version = 1)

  2. Default Global Templates

    OpsRamp has a Global template for each Native Type of Rubrik Cluster. 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: rubrik StorageGRID Template - 1 (i.e, appName = rubrik , nativeType = Rubrik 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: Rubrik Cluster Monitor rubrik Rubrik Cluster 1 (i.e, monitorKey = Rubrik Cluster Monitor, appName = rubrik , nativeType = Rubrik Cluster, version= 1)

Configure and install the integration

  1. From All Clients, select a client.
  2. Go to Setup > Integrations and Apps.
  3. Click Manage Apps.
    • If there are already installed applications, it will redirect to the INSTALLED APPS page where all the installed applications are displayed.
    • If there are no installed applications, it will navigate to the ADD APP page.
  1. 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.
  1. Click ADD in the Rubrik application.
  2. In the Configuration page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
NameEnter the name for the configuration.
Rubrik Cluster IP Address/Host NameEnter the Host name or the IP address.
Rubrik REST API PortAPI Port information
CredentialSelect the credentials from the drop-down list.
Note: Click + Add to create a credential.


  • By default the Is Secure checkbox is selected.
  • Select the following:
    • App Failure Notifications: if enabled,
      • an alert will be sent to the registered gateway resource.
      • an alert is raised for connectivity, authentication exception,
        • Discovery - alert will be on a gateway resource that is registered with the application.
        • Monitoring - alert will be on a particular Powerflex resource.
    • Alert Configuration: enables integrating third party alerts into OpsRamp using further configurations.
  • Below are the default values set for:
    • alertSeverity: provides severity alerts that get integrated out of all possible alerts.
      • Default Values: Critical, Warning.
      • Possible Values: Critical, Warning.
    • Alert Severity Mapping: enables you to map the severities between Dell PowerFlex and OpsRamp as severities are predefined values in each system.
      • Possible values of Alert Severity Mapping Filter configuration property are {“Critical”:“Critical”,“Warning”:“Warning”}
        Note: You can change it as per your business use cases at any point in time from the Configuration page.
  1. Select the below mentioned Custom Attribute:
Custom AttributeSelect the custom attribute from the drop down list box.
ValueSelect the value from the drop down list box.

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).

  1. 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.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.
  1. 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.
  2. Click Next.
  3. In the Installation page, select an existing registered profile, and click FINISH.

The application is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.

Modify the Configuration

View the Rubrik details

The discovered resource(s) are displayed in Infrastructure > Resources > Server, with Native Resource Type as Rubrik Node. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for Rubrik Node.


Resource Type Filter Keys

Rubrik application resources are filtered and discovered based on below keys.

Resource TypeSupported Input Keys
All TypesresourceName
Rubrik ClusterVersion
API Version
Registered Mode
Rubrik DiskDisk Type
Node Id

Supported metrics

Native TypeMetric NamesDisplay NameUnitDescription
Rubrik Clusterrubrik_cluster_runwayRemainingRubrik Cluster Runway RemainingDaysNumber of days remaining before the system fills up.
rubrik_cluster_StatusRubrik Cluster StatusStatus of the Rubrik cluster.
rubrik_cluster_StorageUsageRubrik Cluster Storage UsageGBUsed storage of the Rubrik cluster.
rubrik_cluster_StorageUtilizationRubrik Cluster Storage Utilization%Storage utilization of the Rubrik cluster.
rubrik_cluster_PhysicalDataIngestionRubrik Cluster Physical Data IngestionBytes/secPhysical data ingestion of the Rubrik cluster.
rubrik_cluster_ReadIOPSRubrik Cluster Read IOPSIOPSRead IOPS of Rubrik cluster.
rubrik_cluster_WriteIOPSRubrik Cluster Write IOPSIOPSWrite IOPS of Rubrik cluster.
rubrik_cluster_ReadIOThroughputRubrik Cluster Read IO ThroughputBytes/secReadIO throughput statistics of Rubrik cluster.
rubrik_cluster_WriteIOThroughputRubrik Cluster Write IO ThroughputBytes/secWriteIO throughput statistics of Rubrik cluster.
rubrik_task_SuccessCountRubrik Task Success CountcountSuccess count of tasks on Rubrik cluster.
rubrik_task_FailureCountRubrik Task Failure CountcountFailure count of tasks on Rubrik cluster.
rubrik_job_SuccessCountRubrik Job Success CountcountSuccess count of jobs run in the last 24 hours.
rubrik_job_FailureCountRubrik Job Failure CountcountFailure count of jobs run in the last 24 hours.
rubrik_job_TotalCountRubrik Job Total CountcountTotal count of jobs run in the last 24 hours.
rubrik_job_ActiveCountRubrik Job Active CountcountActive jobs running for the last 24 hours.
rubrik_job_CanceledCountRubrik Job Canceled CountcountCanceled jobs in the last 24 hours.
rubrik_cluster_RegisteredHostStatusRubrik Cluster Registered Host StatusConnection status of hosts registered to Rubrik cluster.
Rubrik Noderubrik_node_StatusRubrik Node StatusStatus of the Rubrik cluster node.
rubrik_node_ReadIOPSRubrik Node Read IOPSIOPSRubrik cluster node read IOPS.
rubrik_node_WriteIOPSRubrik Node Write IOPSIOPSRubrik cluster node write IOPS.
rubrik_node_ReadIOThroughputRubrik Node Read IO ThroughputBytes/secRubrik cluster node read IO throughput.
rubrik_node_WriteIOThroughputRubrik Node Write IO ThroughputBytes/secRubrik cluster node write IO throughput.
Rubrik Diskrubrik_disk_StatusRubrik Disk StatusStatus of the Rubrik cluster node disk.
rubrik_disk_UsageRubrik Disk UsageGBRubrik cluster node disk usage.
rubrik_disk_UtilizationRubrik Disk Utilization%Rubrik cluster node disk utilization.

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 not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
  • 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.
    Note: Not supported with Cluster Gateway.
  • No support of showing activity log and applied time.
  • Event polling Critical alerts generated based on “event_series_status” category “Failure” events.
  • Coming to the challenge with event monitoring, we could not relate a Failure event with a subsequent heel event. So because of this there won’t be any healing mechanism from the application side. The customer has to heal the alerts manually in every case.