ServiceNow CIS - Discovery (New York) Latest Version Rated A+

ServiceNow CIS - Discovery (New York) Latest Version Rated A+ Cloud Discovery Cloud discovery finds resources in AWS and Azure clouds, and then populates the CMDB with the relevant CIs and relationships. Two types: 1. Service account cloud discovery 2. Cloud application discovery Server-less Discovery Discovery can find applications on host machines without the need to discover the host first. Two types: 1. Standard server-less discovery 2. Host-based server-less discovery Discovery Dashboard displays 1. The current progress (status) of the actively running Discovery schedules. 2. Newly discovered devices and applications, by time discovered. 3. Existing devices and applications not updated by Discovery. 4. Errors that occurred during a Discovery schedule that has run. 5. Credentials that were either not required or unused by a Discovery schedule. 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 Discovery Status form. What are the Discovery Status reference lists? 1. Discovery Log: Classification failures, CMDB updates, and authentication failures. 2. Devices: Summary of all the devices scanned during discovery, and what action sensors took on the CMDB. 3. ECC Queue: Connected flow of probe and sensor activity, actual XML payload. 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. Discovery Log 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. Discovery Pattern Log The Pattern Discovery log includes Horizontal Discovery log records, which display information about discoveries that were performed with patterns. A horizontal discovery log record is created for an entire horizontal discovery run, which includes the results of all the operations specified in the pattern. Why use Discovery status? To see a summary of a Discovery, access the ECC queue, as well as the actual XML payload. MID Server Fail-Over Behavior in a Cluster MID Servers in a fail-over cluster each have a configured order that the platform uses to determine which MID Server to use next in case of failure. MID Servers in a fail-over cluster work independently and do not load balance with other MID Servers in that cluster (although they might also be members of load balancing clusters). When a MID Server fails, the MID Server Cluster Management business rule selects the highest available MID Server in the order to take over the work. The selected MID Server checks the ECC Queue and starts with jobs that are either Processing or Ready.