Schedule Discovery on a service account

You can schedule the Discovery of logical datacenters (LDCs) that runs automatically at specified intervals.

Before you begin

Role required: sn_cmp.cloud_admin

About this task

If you upgraded from the previous version of the Cloud Management application and you still have this service account configured on a Discovery schedule, Discovery could run twice on the account. Make sure that you disable any old Discovery schedules that use this cloud account.


  1. Navigate to Cloud Management > Service Accounts.
  2. Click the name of a service account.
  3. Click Create Discovery Schedule.
  4. Fill out the form fields (see table).
    Field Description
    Name Enter a unique, descriptive name for your schedule.
    Discover Keep this option Cloud Resources.
    Max Run Time Set a time limit for running this schedule. When the configured time elapses, the remaining tasks for the discovery are canceled, even if the scan is not complete. Use this field to limit system load to a desirable time window. If no value is entered in this field, this schedule runs until complete.
    Run Determines the run schedule of the discovery. Configure the frequency in the Run field and the other fields that appear to specify an exact time.
    Note: The run time always uses the system time zone. If you add the optional Run as time zone field, it has no effect on the actual runtime.
    Table 1. Discovery schedule run options
    Run option Description
    Daily Runs every day. Use the Time field to select the time of day this discovery runs.
    Weekly Runs on one designated day of each week. Use the Time field to select the time of day this discovery runs.
    Monthly Runs on one designated day of each month. Use the Day field to select the day of the month. Use the Time field to select the time of day this discovery runs. If the designated day does not occur in the month, the schedule does not run that month. For example, if you designate day 30, the schedule does not run in February.
    Periodically Runs every designated period of time. Use the Repeat Interval field to define the period of time in days, hours, minutes and seconds. The first discovery runs at the point in time defined in the Starting field. The subsequent discoveries run after each Repeat Interval period passes.
    Once Run one time as designated by the date and time defined in the Starting field.
    On Demand Does not run on a schedule. Click the Discover now link to run this discovery.
    Weekdays Runs every Monday, Tuesday, Wednesday, Thursday, and Friday. Use the Time field to select the time of day.
    Weekends Runs every Saturday and Sunday. Use the Time field to select the time of day.
    Month Last Day Run the last day of every month. Use the Time field to select the time of day.
    Calendar Quarter End Runs on March 31, June 30, September 30, and December 31. Use the Time field to select the time of day. To change these dates, modify the script include DiscoveryScheduleRunType.
    After Discovery Allows you to sequentially stagger the schedule. Use this option to run this schedule after the Discovery designated in the Run after field finishes. Check the Even if canceled check box to designate that this discovery should run even if the Run after Discovery is canceled before it finishes.
    • This option is not valid when the Discovery is started via DiscoverNow, or when using the Discover CI feature.
    • You cannot designate an inactive Discovery schedule.
    • You cannot create a loop by designating the run after Discovery to be the same Discovery.
    • This Discovery does not run if the Run after discovery does not finish, with the exception that the Even if canceled box is checked and the Discovery is canceled.


Discovery runs at the specified times. After Discovery finishes, discovered datacenters appear in the Logical Datacenters Related list.

If you configured a Discovery schedule, it appears in the Discovery Config- Logical Datacenters related list. To run discovery on a single datacenter, add the datacenter to the discovery schedule in this related list, then run Discovery again.

Open a datacenter record to see the relationships the datacenter has with other CIs, including the discovered resources in that datacenter.
Figure 1. Resources in an AWS datacenter
Resources in an AWS datacenter

What to do next

Set up your cloud accounts. You can also check the Cloud API Trail to troubleshoot a failed discovery.