Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Operations Management
Table of Contents
Choose your release version
    Home New York IT Operations Management IT Operations Management ITOM Visibility Discovery Running discoveries in your network Cloud Discovery Using the Discovery Manager

    Using the Discovery Manager

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Using the Discovery Manager

    Use the Discovery Manager wizard to quickly create a schedule for discovering elements of your cloud service account. Specify your provider account, the MID Servers to use, and the datacenters you want to discover. Optionally, you can schedule a deep discovery of the running applications on the virtual machines that are discovered for a selected cloud service account.

    Accessing the Discovery Manager

    To access the Discovery Manager, navigate to Discovery > Home. Click Discover Cloud Resources in the Welcome screen to begin configuring a schedule to discover your cloud resources.
    Cloud Discovery welcome screen
    Note: The Welcome screen contains a link to the Discovery Quick Start. This wizard is designed to get you up and running with a basic Discovery quickly. Use the Quick Start to evaluate Discovery or to explore new network devices. It is not intended for discovering your cloud resources.
    If the system cannot detect a MID Server, you are prompted to install and configure one, using MID Server Guided Setup. This notice also displays if an existing MID Server is not available because it is upgrading.
    Notification that no MID Servers were found

    Discovery Manager interface

    Use the Discovery Manager to input the information you need to access your service accounts and sub-accounts, including credentials and MID Servers. Test the connections to your accounts and then create schedules to execute Discovery on the cloud resources in the datacenters you have selected.

    Progress indicator
    As you complete each configuration phase, tabs at the top of the Discovery Manager track your progress. A check mark indicates a completed phase. A dark underline marks the current phase. The tabs are interactive, so you can move to a phase by clicking on that tab.
    Discovery Manager progress indicator

    Select a service account and test your credentials

    The Cloud Discovery wizard begins with the account selection and testing phase. Specify your cloud provider and select the service account to discover. Discovery allows you to include one or all available sub-accounts (AWS only) on the schedule. Provide the credentials for the cloud service account and test the connection.

    Before you begin

    Before you attempt to configure Cloud Discovery, you must have at least one validated MID Server, with a status of Up, that is capable of reaching the IP ranges you intend to discover. You can install the MID Server using Guided Setup or by manually downloading and running the installer. For details, see the MID Server installation instructions for Linux and Windows. Make sure you configure MID Servers used for Cloud Discovery with the Cloud Management capability.

    Role required: discovery_admin, admin

    About this task

    The cdu.record.watcher.timeout system property defines the maximum waiting period for these Cloud Discovery configuration processes to run:
    • Service account validation
    • Member account Discovery
    • Discovery of logical datacenters
    The default timeout value is 120,000 milliseconds, or 2 minutes.

    Procedure

    1. In the Basic Info pane of the Discovery Manager, select the name of your cloud provider, such as AWS.
    2. In the Schedule Name field, enter a unique and descriptive name for this schedule.
      The wizard displays the count of the validated and available MID Servers.
    3. If no MID Servers have the Cloud Management capability, click Configure MID Servers and configure a MID Server appropriately.
      1. Navigate to MID Servers > Capabilities.
      2. Select the Cloud Management capability.
        You can also select the ALL capability, which includes Cloud Management by default.
      3. Click Edit in the MID Servers related list, and then add your MID Servers to the capability.
      4. Click Save.
        Your MID Servers are ready to communicate with your cloud service accounts.
        Service provider and schedule name
    4. In the Service Accounts pane, select the existing account for the newly named schedule.
      If you select an existing account, the system auto-completes the form with the available information. If you add an account, you must provide the account ID, credentials, and URL, if applicable. For VMware, the URL is mandatory.
      • The AWS account ID is the 12-digit account number.
      • The Azure account ID is the Subscription ID.
      • The IBM account ID is also called the Account ID.
      • The GCP account ID is the Project ID.
      • The VMware account ID is the virtual machine instance UUID.
      Note: VMware discovery can run without a service account. To discover VMware resources, configure the schedule to run on the IP address of the vCenter server.
    5. Select the credentials for this cloud service account or add new credentials.
      1. To add a credential, click the plus icon (+).
      2. Select the appropriate cloud credential type from the list.
      3. Complete the form and click Save.
        Note: AWS users can configure AWS to generate temporary credentials for service accounts. This capability eliminates the need to define some credentials on the instance and can be used to increase security on your sub-accounts. For details, see Assume an AWS role for temporary cloud Discovery credentials.
      Add a new provider account
    6. Click Test Account to validate the account with the details provided.
      Messages in the header bar notify you of the validation results. If you specified a master account and the connection test was successful, the wizard displays a selection screen for any sub-accounts associated with the master account. By default, all current sub-accounts are selected for the schedule and cannot be moved to the Available list.
      Note: If the validation process does not return any sub-accounts or sub-accounts that you added recently, click Refresh Members or re-run the validation process. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.
      Select sub-accounts to include in the schedule
    7. To select specific sub-accounts for the schedule, deactivate the auto-select feature.
      By default, all sub-accounts are selected. To disable the feature and to permit the selection of specific datacenters to discover, slide the toggle switch to the left.
      Disabling the auto-select feature for sub-accounts
    8. Drag and drop the sub-accounts you want to exclude from the schedule from the Selected list to the Available list.

    Select a cloud provider datacenter to discover

    Discovery displays the list of available datacenters when you validate the service account. Specify which datacenters you want to discover with this schedule.

    Before you begin

    Role required: discovery_admin, admin

    Procedure

    1. To select the datacenters to discover, click the Select Datacenters phase in the Discovery Manager tab bar.
      By default, all datacenters associated with your service account are selected for the schedule.
      Note: If no datacenters appear, click Refresh Datacenters or re-run the account validation. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.
      Selecting datacenters for Discovery
    2. To select specific datacenters for the schedule, deactivate the auto-select feature by moving the toggle switch to the left.
    3. Drag and drop the datacenters you want to discover from the Available list to the Selected list.
    4. Click the next phase in the tab bar.
      Optionally, you can configure IP ranges to discover virtual machines (VM), or move to the schedule phase and complete Cloud Discovery setup.

    Enable virtual machine Discovery in your cloud environment

    Virtual machine (VM) Discovery is an optional configuration that performs a deep discovery of the virtual machines identified by the cloud schedule, using the IP addresses of the VMs. VM Discovery is enabled by default in the Discovery Manager wizard.

    Before you begin

    All MID Servers you intend to use for Cloud Discovery must be validated, have a status of Up, and be able to access the IP ranges in your cloud provider account.
    Attention: The upgrade process from Madrid to New York deactivates existing schedules for the discovery of cloud resources. Make sure to re-activate any schedules in the Discovery Manager that might have been deactivated during an upgrade from Madrid. These schedules have a Run status of undefined in the list view of the Discovery Schedule [discovery_schedule] table.

    Role required: admin

    About this task

    You do not need to configure IP ranges for the MID Servers used with Cloud Discovery. Discovery automatically selects the IP addresses of the virtual machines in the datacenters you selected in the wizard.

    Procedure

    1. To discover the VMs that are part of the current schedule, click the Discover Virtual Machines (optional) phase in the Discovery Manager tab bar.
      By default, VM discovery is active.
    2. Select the MD Server to use.
      The available MID Server selection types are:
      • Auto-Select MID Server: Discovery selects an appropriate MID Server automatically.
      • Specific MID Cluster: Discovery uses the named MID Server cluster.
      • Specific MID Server: Discovery uses the named MID Server.
      Configure VMs to discover
    3. To prevent VM Discovery from running, toggle the activation switch to the left.
      The MID Selection Type field disappears.
    4. When you have completed this configuration, click the Create Schedule phase in the tab bar.

    Create a Cloud Discovery schedule

    The final phase in the Discovery Manager wizard creates the schedule that triggers Cloud Discovery.

    Before you begin

    Role required: admin, discovery_admin

    About this task

    You can also access the schedule phase of the Discovery Manager from the Discovery Schedule form. Navigate to Discovery > Discovery Schedules and click Cloud Discovery in the schedules list.

    Procedure

    1. To configure the Cloud Discovery schedule, click Create Schedule in the Discovery Manager tab bar.
      By default, the schedule is active.
    2. Configure when and how often the schedule should run and define a timeout threshold if you want to restrict Cloud Discovery to a specific duration.
      Cloud Discovery schedule
    3. To deactivate the schedule, toggle the switch to the left.
      This prevents Cloud Discovery from running.
    4. Complete the Cloud Discovery configuration process by selecting one of these options:
      • Finish and Run: Runs Discovery immediately, using the current configuration. All subsequent cloud discoveries run on the schedule you provided.
      • Finish: Exits the wizard and runs Cloud Discovery on the schedule you provided.
    5. Open the Discovery Home page and view the results of your cloud Discovery.
    Related concepts
    • Cloud Discovery account credentials
    • Assume an AWS role for temporary cloud Discovery credentials

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Using the Discovery Manager

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Using the Discovery Manager

      Use the Discovery Manager wizard to quickly create a schedule for discovering elements of your cloud service account. Specify your provider account, the MID Servers to use, and the datacenters you want to discover. Optionally, you can schedule a deep discovery of the running applications on the virtual machines that are discovered for a selected cloud service account.

      Accessing the Discovery Manager

      To access the Discovery Manager, navigate to Discovery > Home. Click Discover Cloud Resources in the Welcome screen to begin configuring a schedule to discover your cloud resources.
      Cloud Discovery welcome screen
      Note: The Welcome screen contains a link to the Discovery Quick Start. This wizard is designed to get you up and running with a basic Discovery quickly. Use the Quick Start to evaluate Discovery or to explore new network devices. It is not intended for discovering your cloud resources.
      If the system cannot detect a MID Server, you are prompted to install and configure one, using MID Server Guided Setup. This notice also displays if an existing MID Server is not available because it is upgrading.
      Notification that no MID Servers were found

      Discovery Manager interface

      Use the Discovery Manager to input the information you need to access your service accounts and sub-accounts, including credentials and MID Servers. Test the connections to your accounts and then create schedules to execute Discovery on the cloud resources in the datacenters you have selected.

      Progress indicator
      As you complete each configuration phase, tabs at the top of the Discovery Manager track your progress. A check mark indicates a completed phase. A dark underline marks the current phase. The tabs are interactive, so you can move to a phase by clicking on that tab.
      Discovery Manager progress indicator

      Select a service account and test your credentials

      The Cloud Discovery wizard begins with the account selection and testing phase. Specify your cloud provider and select the service account to discover. Discovery allows you to include one or all available sub-accounts (AWS only) on the schedule. Provide the credentials for the cloud service account and test the connection.

      Before you begin

      Before you attempt to configure Cloud Discovery, you must have at least one validated MID Server, with a status of Up, that is capable of reaching the IP ranges you intend to discover. You can install the MID Server using Guided Setup or by manually downloading and running the installer. For details, see the MID Server installation instructions for Linux and Windows. Make sure you configure MID Servers used for Cloud Discovery with the Cloud Management capability.

      Role required: discovery_admin, admin

      About this task

      The cdu.record.watcher.timeout system property defines the maximum waiting period for these Cloud Discovery configuration processes to run:
      • Service account validation
      • Member account Discovery
      • Discovery of logical datacenters
      The default timeout value is 120,000 milliseconds, or 2 minutes.

      Procedure

      1. In the Basic Info pane of the Discovery Manager, select the name of your cloud provider, such as AWS.
      2. In the Schedule Name field, enter a unique and descriptive name for this schedule.
        The wizard displays the count of the validated and available MID Servers.
      3. If no MID Servers have the Cloud Management capability, click Configure MID Servers and configure a MID Server appropriately.
        1. Navigate to MID Servers > Capabilities.
        2. Select the Cloud Management capability.
          You can also select the ALL capability, which includes Cloud Management by default.
        3. Click Edit in the MID Servers related list, and then add your MID Servers to the capability.
        4. Click Save.
          Your MID Servers are ready to communicate with your cloud service accounts.
          Service provider and schedule name
      4. In the Service Accounts pane, select the existing account for the newly named schedule.
        If you select an existing account, the system auto-completes the form with the available information. If you add an account, you must provide the account ID, credentials, and URL, if applicable. For VMware, the URL is mandatory.
        • The AWS account ID is the 12-digit account number.
        • The Azure account ID is the Subscription ID.
        • The IBM account ID is also called the Account ID.
        • The GCP account ID is the Project ID.
        • The VMware account ID is the virtual machine instance UUID.
        Note: VMware discovery can run without a service account. To discover VMware resources, configure the schedule to run on the IP address of the vCenter server.
      5. Select the credentials for this cloud service account or add new credentials.
        1. To add a credential, click the plus icon (+).
        2. Select the appropriate cloud credential type from the list.
        3. Complete the form and click Save.
          Note: AWS users can configure AWS to generate temporary credentials for service accounts. This capability eliminates the need to define some credentials on the instance and can be used to increase security on your sub-accounts. For details, see Assume an AWS role for temporary cloud Discovery credentials.
        Add a new provider account
      6. Click Test Account to validate the account with the details provided.
        Messages in the header bar notify you of the validation results. If you specified a master account and the connection test was successful, the wizard displays a selection screen for any sub-accounts associated with the master account. By default, all current sub-accounts are selected for the schedule and cannot be moved to the Available list.
        Note: If the validation process does not return any sub-accounts or sub-accounts that you added recently, click Refresh Members or re-run the validation process. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.
        Select sub-accounts to include in the schedule
      7. To select specific sub-accounts for the schedule, deactivate the auto-select feature.
        By default, all sub-accounts are selected. To disable the feature and to permit the selection of specific datacenters to discover, slide the toggle switch to the left.
        Disabling the auto-select feature for sub-accounts
      8. Drag and drop the sub-accounts you want to exclude from the schedule from the Selected list to the Available list.

      Select a cloud provider datacenter to discover

      Discovery displays the list of available datacenters when you validate the service account. Specify which datacenters you want to discover with this schedule.

      Before you begin

      Role required: discovery_admin, admin

      Procedure

      1. To select the datacenters to discover, click the Select Datacenters phase in the Discovery Manager tab bar.
        By default, all datacenters associated with your service account are selected for the schedule.
        Note: If no datacenters appear, click Refresh Datacenters or re-run the account validation. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.
        Selecting datacenters for Discovery
      2. To select specific datacenters for the schedule, deactivate the auto-select feature by moving the toggle switch to the left.
      3. Drag and drop the datacenters you want to discover from the Available list to the Selected list.
      4. Click the next phase in the tab bar.
        Optionally, you can configure IP ranges to discover virtual machines (VM), or move to the schedule phase and complete Cloud Discovery setup.

      Enable virtual machine Discovery in your cloud environment

      Virtual machine (VM) Discovery is an optional configuration that performs a deep discovery of the virtual machines identified by the cloud schedule, using the IP addresses of the VMs. VM Discovery is enabled by default in the Discovery Manager wizard.

      Before you begin

      All MID Servers you intend to use for Cloud Discovery must be validated, have a status of Up, and be able to access the IP ranges in your cloud provider account.
      Attention: The upgrade process from Madrid to New York deactivates existing schedules for the discovery of cloud resources. Make sure to re-activate any schedules in the Discovery Manager that might have been deactivated during an upgrade from Madrid. These schedules have a Run status of undefined in the list view of the Discovery Schedule [discovery_schedule] table.

      Role required: admin

      About this task

      You do not need to configure IP ranges for the MID Servers used with Cloud Discovery. Discovery automatically selects the IP addresses of the virtual machines in the datacenters you selected in the wizard.

      Procedure

      1. To discover the VMs that are part of the current schedule, click the Discover Virtual Machines (optional) phase in the Discovery Manager tab bar.
        By default, VM discovery is active.
      2. Select the MD Server to use.
        The available MID Server selection types are:
        • Auto-Select MID Server: Discovery selects an appropriate MID Server automatically.
        • Specific MID Cluster: Discovery uses the named MID Server cluster.
        • Specific MID Server: Discovery uses the named MID Server.
        Configure VMs to discover
      3. To prevent VM Discovery from running, toggle the activation switch to the left.
        The MID Selection Type field disappears.
      4. When you have completed this configuration, click the Create Schedule phase in the tab bar.

      Create a Cloud Discovery schedule

      The final phase in the Discovery Manager wizard creates the schedule that triggers Cloud Discovery.

      Before you begin

      Role required: admin, discovery_admin

      About this task

      You can also access the schedule phase of the Discovery Manager from the Discovery Schedule form. Navigate to Discovery > Discovery Schedules and click Cloud Discovery in the schedules list.

      Procedure

      1. To configure the Cloud Discovery schedule, click Create Schedule in the Discovery Manager tab bar.
        By default, the schedule is active.
      2. Configure when and how often the schedule should run and define a timeout threshold if you want to restrict Cloud Discovery to a specific duration.
        Cloud Discovery schedule
      3. To deactivate the schedule, toggle the switch to the left.
        This prevents Cloud Discovery from running.
      4. Complete the Cloud Discovery configuration process by selecting one of these options:
        • Finish and Run: Runs Discovery immediately, using the current configuration. All subsequent cloud discoveries run on the schedule you provided.
        • Finish: Exits the wizard and runs Cloud Discovery on the schedule you provided.
      5. Open the Discovery Home page and view the results of your cloud Discovery.
      Related concepts
      • Cloud Discovery account credentials
      • Assume an AWS role for temporary cloud Discovery credentials

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login