Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Create a pattern for standard serverless discovery

Create a pattern for standard serverless discovery

To find application CIs that reside on an unknown host, create an infrastructure pattern for standard serverless discovery. In the pattern, you must specify input parameters to explore the CI.

Before you begin

Role required: cloud_admin, sm_admin, or admin


  1. Navigate to Pattern Designer > Discovery 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 modify patterns 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 url 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.
  11. After you connect and run the operation, the Output field displays the content.


In the following 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, you click Debug Mode, enter the URL, and click Connect,

Figure 1. Example debugging of an HTTP Get Call
Example debugging of an HTTP Get Call

After the operation executes, the XML on the website appears in the Output window.

What to do next

Use the pattern in a serverless discovery schedule.

Create a Discovery schedule for standard serverless discovery

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

About this task

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


  1. Navigate to Discovery > Schedules.
  2. Click New.
  3. Select Serverless in the Discovery field. See Schedule horizontal discovery 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):
    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.
  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 Volume 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.


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.

This site is scheduled for a small content update on Tuesday, December 18th, between the hours of 4:00pm and 8:00pm Pacific Time (Dec 19 00:00 – Dec 19 4:00 UTC). Access to this site may be slightly delayed during that time.