---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create a serverless discovery schedule

# Create a serverless discovery schedule for Rubrik cluster discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 27, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Set up a dedicated discovery schedule for each Rubrik cluster (Brik) to identify cluster resources using a serverless pattern and credential alias.

## Before you begin

* Verify the MID Server is set to Active and can reach the target Rubrik cluster.
* Create an alias for the basic authentication credential. For more information, see [Create a basic authentication credential alias for Rubrik discovery](https://servicenow-prod.fluidtopics.net/ACuhmNW55~mdVYsoBYACQA "Create an alias and add it to a basic authentication credential to discover Rubrik clusters.").
* Obtain the IP address of one of the Rubrik nodes in the target cluster.

{#create-serverless-schedule-rubrik__ul_x1b_ylv_rubrik}

Role required: discovery_admin

## About this task

Each Rubrik cluster (Brik) requires a separate serverless discovery schedule. Each schedule must include the IP address of one of the Rubrik nodes in that cluster, and the
credential alias associated with the Rubrik basic authentication credential record.{#create-serverless-schedule-rubrik__create-serverless-schedule-rubrik-context-1}

## Procedure

1. Navigate to AllDiscoveryDiscovery Schedules.
2. Create the discovery schedule record.
   1. Select New.
   2. On the form, fill in the fields.  
      {#create-serverless-schedule-rubrik__table_qtq_3qk_rubrik__entry__2}

      | Field | Description |
      |-|-|
      | Name | Unique name for this discovery schedule. For example, <kbd class="ph userinput">Discover Rubrik</kbd>. |
      | Discover | Scan type. Select Serverless. |
      | MID server | Name of the MID Server to use for this schedule. |
      | Active | When selected, activates this schedule for discovery runs. |
      [Table 1. Discovery Schedule form]

      {#create-serverless-schedule-rubrik__table_qtq_3qk_rubrik}
   3. Select Submit.
   {#create-serverless-schedule-rubrik__substeps_lyc_z4k_rubrik}
3. Create the execution pattern.
   1. In the Discovery Schedules page, select the record you created.
   2. In the Serverless Execution Patterns tab, select New.
   3. On the form, fill in the fields.  
      {#create-serverless-schedule-rubrik__table_tvt_glv_rubrik__entry__2}

      | Field | Description |
      |-|-|
      | Name | Descriptive name for this record. |
      | Pattern | Pattern to use for this schedule. Select the Rubrik cluster (LP) pattern. |
      | Run Child Patterns | Set to true for each Rubrik discovery pattern. All child patterns associated with the Rubrik discovery pattern run automatically. This behavior is required by the Large Payload (LP) mechanism, which discovers the Rubrik cluster and all corresponding CI types. |
      | Active | When selected, activates this schedule for discovery runs. |
      [Table 2. Serverless Execution Pattern form]

      {#create-serverless-schedule-rubrik__table_tvt_glv_rubrik}
   4. Select Submit.
   {#create-serverless-schedule-rubrik__substeps_ahb_mqk_rubrik}
4. Set the pattern launcher parameters.
   1. In the Discovery Pattern Launcher Parameters tab, select the record you created.
   2. On the form, fill in the fields.  
      {#create-serverless-schedule-rubrik__table_zkw_j1w_rubrik__entry__2}

      | Parameter | Value |
      |-|-|
      | ip_address | IP address of one of the Rubrik nodes in the cluster. |
      | credential_alias | ID of the credential alias you created for the Rubrik Basic Auth credential record. |
      [Table 3. Pattern launcher parameters]

      {#create-serverless-schedule-rubrik__table_zkw_j1w_rubrik}
   3. Select Submit.
   {#create-serverless-schedule-rubrik__substeps_m4g_xqk_rubrik}
{#create-serverless-schedule-rubrik__steps_svt_glv_rubrik}

## What to do next

Either execute discovery immediately by selecting Discover now or wait until the predefined schedule triggers the discovery.
**Related reference**   

* [Rubrik Cluster discovery](https://servicenow-prod.fluidtopics.net/hbFPTVvLeVEtweHUKurobw "Discovery uses multiple patterns to find all Rubrik cluster data. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")

*[\>]: and then