Discovery Schedule form reference
The Discovery Schedule form provides details about the configuration items (CIs) targeted for discovery, the associated MID Server, and the schedule settings for when and how the discovery runs.
For instructions on this procedure, see Schedule a horizontal discovery.
| Field | Description |
|---|---|
| Name | Enter a unique, descriptive name for your schedule. |
| Discover | Select one of the following scan types:
|
| MID Server selection method | Select the method that Discovery uses to select a MID Server:
Remarque :
The discovery schedule enforces domain separation. The MID Servers that are available for selection are limited to the same domain of the user who is configuring the schedule. See MID Server selection sequence for Discovery schedules for additional information. |
| MID Server | Select the MID Server to use for this schedule. This field is available if MID Server selection method is set to Specific MID Server, or if you discover IP
addresses, networks, or web services. To verify that the MID Server you selected is up and validated, look at the MID Server dashboard. |
| MID Server Cluster | Select the MID Server cluster to use for this schedule. This field is available if MID Server selection method is set to Specific MID Cluster. |
| Behavior | Select a behavior configured for the MID Servers in your network. This field is available only if MID Server selection method is set to Use Behavior. |
| Active | Select the check box to enable this schedule. If you clear the check box, the schedule is inactive, but you can still run a discovery manually from this form, using the configured values. |
| Location | Choose a location to assign to the CIs that the schedule discovers. If this field is empty, then no location is assigned. |
| 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 isn’t 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. |
| Max Idle time | Set a time limit for inactivity during discovery to automatically cancel stalled processes and log the event. A discovery is considered idle only when no input records are being processed and nothing
is left in the processing state. Idle time is measured from the most recent change to an ECC Queue record. The configured idle time is fixed at the start of the discovery and won’t reflect any edits until
the next run. If no value is entered in this field, this schedule runs until complete or canceled. Remarque : By default, the Max Idle time field doesn’t display in the Discovery Schedule
form. To include this parameter, open the Discovery Schedules [discovery_schedule] table, add the column, and configure the Max Idle time directly in the table. For information about customizing
columns in tables, see Personalize a list. |
| Run and related fields | 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. Remarque : The run time uses the
system time zone. If you add the optional Run as tz field, it has no effect on the actual runtime. |
| Log state changes | Select this check box to create a log entry every time the state changes during a discovery, such as a device going from Active to Classifying. View the discovery states from the Discovery Devices related list on the Discovery Status form. The Completed activity and Current activity fields display the states. |
| Shazzam batch size | Enter the number of IP addresses that each Shazzam probe can scan. Dividing the IP addresses into batches improves performance by enabling classification for each batch to begin after the batch
completes, rather than after all IP addresses have been scanned. The probes run sequentially. For example, the value is set to 1000 and a discovery scans 10,000 IP addresses using a single MID Server. It creates 10 Shazzam probes with each probe scanning 1000 IP addresses. By default, the batch size is 1000. A UI policy enforces a minimum batch size of 256 because batch
sizes below 256 IP addresses don’t benefit from clustering. The policy converts any value below 256 to a value of zero. The value for this field can’t exceed the value defined in the maximum range size property for the Shazzam probe. |
| Discovery Agent | Select the agent to perform this discovery:
By default, the Discovery Agent is set to MID. This field is available only when the system property glide.discovery.enable_ssm is enabled, the Discover type is set to Configuration Items, and the Run after field is configured to follow a Cloud Resources schedule. |
| Shazzam cluster support | Select the check box to distribute Shazzam processing among multiple MID Servers in a cluster and improve performance. This setting works with the Shazzam batch size. For example, a schedule is created to scan 100,000 IP addresses, with 10 MID Servers assigned to do the work. Each MID Server is assigned to scan 10,000 IP addresses. If the Shazzam batch size is set to 5,000 IP addresses per probe, the schedule runs two Shazzam probes per MID Server (10,000 IP addresses/5,000 per batch). These probes are run in sequence and not concurrently. |
| Use SNMP Version | Use this field to designate the SNMP version to use for this discovery. The default value is ALL. You can change this value to v1, v2c, or v3. |
| URL Certificate Batch Size | Define the number of URLs to discover per batch during discovery. Leave the batch size as it is unless recommended to change. |
| Quick ranges | Define IP addresses and address ranges to scan by entering IP addresses in multiple formats (network, range, or list) in a single, comma-delimited string. For more information, see Create a Quick IP range for a Discovery schedule. |
| Discover now | Use this link to immediately start this Discovery. |
| Related lists | |
| IP Ranges | This related list defines the ranges of IP addresses to scan with this schedule. If you’re using a simple CI scan (no behaviors), use this related list to define the IP addresses to discover. Remarque : To
improve security, limit the range of discovery targets to exclude unnecessary networks and devices. |
| Discovery Range Sets | This related list defines each range set in a schedule to scan by one or more Shazzam probes. |
| Discovery Status | This related list displays the results of current and past schedule runs. |
| Global IP Exclusion | This related list displays the global IP exclusion records that apply to this schedule. Active global IP exclusions prevent Discovery from scanning the specified IP addresses across all schedules that discover configuration items, IP addresses, or networks. Global IP exclusion records are managed from . For more information, see Use Global Excludes List for IP addresses and ranges. |
| Discovery Attributes | This related list defines the attributes to apply to CIs discovered within this schedule. Use attributes to set CI field values such as location or asset tag at the schedule, range set, or IP address range level. For more information, see Discovery generic attributes. |
| Certificate URLs | This related list displays the URLs that are discovered using this schedule. You can add or delete URLs from this list. |