Discovery status 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. To access the Discovery Status form, navigate to Discovery > Status and open the status record for a Discovery. Each record in the Status list represents the execution of a Discovery by a schedule and displays such high level information as the date of the Discovery, the mode, the number of probe messages sent to devices, and the number of sensor records that were processed. A status record contains data that can help you troubleshoot a failed discovery. Use this data to troubleshoot the behavior of individual probes and sensors or even run those elements separately. Use the status controls to enter probe/sensor threads at any point for a specific Discovery, and then follow the process in either direction. Refresh: Runs the probe again. You can re-run probes when you encounter a failed Discovery or other unexpected results. Discovery timeline: The Discovery timeline is a graphical display of a discovery, including information about each probe and sensor that was used. Discovery log entries: The Discovery Log shows information such as classification failures, CMDB updates, and authentication failures. A Discovery Log record is created for each action associated with a discovery status. ECC queue entries: Entries in the ECC queue provide you with a connected flow of probe and sensor activity, as well as the actual XML payload that is sent to or from an instance. Device history: The device history provides a summary of all the devices scanned during discovery, and what action sensors took on the CMDB. Note: By default, only 30 days of Discovery records are displayed in the status list at a time. The following Discovery status record shows the discovery of a load balancer using a pattern.Figure 1. Example Discovery status record Field Description Number An auto-generated number for the record. Description How this Discovery was run. Typically, the description is Scheduled, but if you ran Discovery manually from a Schedule, the record would show Discover Now in the Description field. If the scan was performed by the Help the Help Desk application, this value is Help the help desk. Schedule The name of the Discovery schedule. State The state of the discovery: Starting Active Completed Canceled Started and Completed The number of probes started and completed during discovery. Source Optional read-only field that shows the source of the Discovery, such as Schedule Discovery, or Quick Discovery. If the source of the Discovery was from an API call, the source is DiscoveryAPI. From Schedule (Read-only schedule data) Discover Shows the Discovery type. The possible types are: Configuration items, IP addresses, Networks, or Web Service. Max Run Time Displays the maximum amount of time Discovery was permitted to run on this schedule. Include alive Indicates that this Discovery includes devices on which one port responded to the scan, but no ports are open. Such a device is considered to be alive. If this check box is not selected, only active devices with one or more open ports that Discovery can query are displayed. Log state changes Indicates that state changes were logged during this Discovery. These states can be seen in the Last and Current fields in the Discovery Devices list in this form. Cancel a Discovery from a Discovery StatusYou can manually cancel a discovery while it is in progress from the Discovery Status record.Discovery timelinesA Discovery timeline generates a graphical display of a Discovery Status record, including information about each probe and sensor that was used in the discovery. The ECC queue for DiscoveryThe External Communication Channel (ECC) Queue is a connection point between an instance and other systems that integrate with it, most commonly a MID Server.Discovery device historyThe Devices related list in the Discovery Status form provides a summary list of all the devices scanned.Logs for DiscoveryThe Discovery log and Pattern Discovery/Horizontal Discovery log display the activity that takes place during a discovery. Use the logs to debug failed discoveries.