The Discovery pattern log is a log that records the execution of a pattern during Discovery or Service Mapping1.It shows the success or failure of the individual pattern steps, as well as the input and output variables, the CI attributes and relationships, and the errors or warnings2.The ECC Queue is a table that displays the input and output messages from and to MID Servers3.It shows the payload of CI attributes and relationships, the Shazzam probe payload, and the relationships created, but not the success or failure of the individual pattern steps4.The success or failure of the individual pattern steps is specific to the Discovery pattern log and can be used to debug or troubleshoot the pattern execution2.

A /24 subnet IP Range means that there are 256 possible IP addresses in the range, from 0 to 255. A Shazzam batch size of 5000 means that Discovery will send 5000 ICMP packets at a time to scan the IP addresses. Therefore, Discovery will launch the Shazzam probe once for every 5000 IP addresses in the range, or 256 / 5000 = 0.0512 times. Since the number of times must be an integer, Discovery will round up to 1 and launch the Shazzam probe once. However, since the Shazzam probe is launched for each MID Server that is assigned to the Discovery Schedule, the actual number of times will depend on how many MID Servers are available. If there are N MID Servers, then the Shazzam probe will be launched N times, each sending 5000 ICMP packets to the same IP range. Therefore, the total number of times that the Shazzam probe will be launched during discovery is N * 1 = N.

Discovery Schedule form

Shazzam Probe

Discovery IP range

The Put file operation allows the transfer of a file from the MID Server to a target1.This operation can be used to copy files from the MID Server to a target device, such as configuration files, scripts, or binaries2.The Put file operation requires the file path on the MID Server and the file path on the target as inputs2.

1:Put file

2:Define discovery steps

The ECC Queue is the normal connection point between an instance and other systems that integrate with ServiceNow, such as MID Servers1.The ECC Queue displays input and output messages from and to MID Servers2.The actual XML payload that is sent to or from an instance is stored in the ECC Queue3.The ECC Queue also provides a connected flow of probe and sensor activity, as probes are sent from the instance to the MID Server, and sensors are sent from the MID Server to the instance2.

1:ServiceNow Discovery Overview

2:ECC Queue Processing and Debugging, with ''Discovery - Sensors'' used as an example

3:Manage ECC Queue content for a MID Server

Hardware Models are templates that define the attributes and default values for a specific type of hardware configuration item (CI). Hardware Models can have a one-to-many relationship with the following entities:

Assets: An asset is a tangible or intangible resource that is tracked and managed by the organization, such as a laptop, a license, or a contract. A Hardware Model can be associated with multiple assets that share the same characteristics and specifications.

Configuration Items: A CI is any component that needs to be managed in order to deliver an IT service, such as a server, an application, or a user. A Hardware Model can be associated with multiple CIs that share the same characteristics and specifications.

Model Categories: A model category is a classification of Hardware Models based on their function, such as network, storage, or server. A Hardware Model can belong to one or more model categories that define its scope and usage.

Hardware Model

Asset

Configuration Item (CI)

[Model Category]