---
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 standard-discovery pattern and schedule

# Create pattern and schedule for standard serverless discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

To find application CIs that reside on an unknown host, create an infrastructure
pattern for standard serverless discovery. After creating the pattern, create a Discovery
schedule that triggers the pattern.

## Before you begin

Role required: cloud_admin, service_mapping_admin, or admin

## About this task

In the pattern, you must specify input parameters to explore the CI.

## Procedure

1. Navigate to AllPattern DesignerDiscovery Patterns.
2. Click New.
3. Specify an Infrastructure type pattern with the correct CI type that applies to the CIs you want to discover.  
   See [Create or customize patterns](https://servicenow-prod.fluidtopics.net/ZaWnPMmnvybQ8YI3j0l7LA "Create or modify a discovery pattern and define its basic attributes.") for an explanation of all form fields.
4. Create an identification section and save the pattern.
5. Click the Input Parameters tab, and then click New.
6. Enter the parameters that are required to reach the serverless CIs.  
   For example, you could enter <kbd class="ph userinput">url</kbd> to reach a remote resource via an HTTP request.  
   Note:  
   You specify the actual URL in a serverless discovery schedule.
7. Save the pattern.
8. Click the Basic tab, and then click the identification section name to open the pattern designer.
9. Create the steps you need to explore serverless CIs.  
   For example, create an Http Get Call operation to reach a remote resource through a URL. In this case, you would specify the `$url` parameter in the URL field.
10. To test the pattern, click Debug Mode and fill in values for the input parameters.  
    You do not need to enter a value for Proxy Host. In the this example, we are connecting to a website that serves up an XML file. The XML file parsing method is already defined in the Http Get Call operation. To test the pattern operation, click Debug Mode, enter the URL, and click Connect.Figure 1. Example debugging of an HTTP Get Call
11. After you connect and run the operation, the Output field displays the content.

## Create a schedule for standard serverless Discovery {#ariaid-title2}

After you create a pattern for standard serverless discovery, create a Discovery
schedule and specify the pattern. Discovery triggers the pattern from the schedule rather
than from a classifier.

### Before you begin

Ensure you have [basic authentication
credentials](https://www.servicenow.com/docs/access?context=r_BasicAuthCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) for HTTP calls in the pattern.

Role required: cloud_admin, service_mapping_admin, or admin

### About this task

You can reuse this schedule to run the same pattern using different parameters.

### Procedure

1. Navigate to AllDiscoverySchedules.
2. Click New.
3. Select Serverless in the Discovery field.  
   See [Schedule a horizontal discovery](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.") for explanation of other fields.
4. Right-click the form header and select Save.
5. In the Serverless Execution Pattern related list, click New.
6. Fill out the form fields (see table):  
   {#create-serverless-disco-schedule__table_pss_f3m_5z__entry__2}

   | Field | Description |
   |-|-|
   | Name | Provide a descriptive name. |
   | Pattern | Select the pattern you created for standard serverless discovery or for proxy host-based discovery. |
   | Proxy Host | Leave this field empty. This field applies to the host proxy-based scenario. |
   | Active | Keep this check box selected to use the pattern execution definition. |
   [ ]

   {#create-serverless-disco-schedule__table_pss_f3m_5z}
7. Right-click the form header and select Save.
8. In the Discovery Pattern Launcher Parameters related list, add the parameters required by the pattern and provide a value for each one in the Value column.
9. Click Submit.
10. Define as many serverless execution pattern records as needed.  
    You can launch the same pattern, but they should have different parameters.
11. Execute discovery by clicking Discover Now or wait until the schedule triggers the discovery.

### Result

Check the Discovery status to see the Discovery log, the devices
list, which holds the discovered CIs, and the ECC queue records. Note that the Shazzam probe
did not launch and Discovery did not trigger any classification probes.
**Related concepts**   

* [Discovery status](https://servicenow-prod.fluidtopics.net/DspthDiBn~da7_tOJabX1Q "The Discovery status provides a summary of a Discovery launched from a schedule. You can also cancel a Discovery that is in progress from the status form.")

*[\>]: and then