The ECC Queue tab displays the input and output messages from and to MID Servers. The default fields that are displayed on this tab are:

Topic : The topic of the message, such as Discovery, Orchestration, or MID Server.

Queue : The queue name of the message, such as input, output, or error.

Source : The source of the message, such as the MID Server name, the instance name, or the probe name.

State : The state of the message, such as ready, processed, or ignored.

Created : The date and time when the message was created.

Updated : The date and time when the message was last updated.

Some other fields that can be added to the ECC Queue tab are:

Details : The details of the message, such as the payload, the response, or the error message.

Pattern log link : The link to the pattern log file, if the message is related to a pattern execution.

CMDB CI : The configuration item that is associated with the message, if any.

Discovery schedule name : The name of the discovery schedule that triggered the message, if any.

 A scheduled job is a background process that runs at a specified time or interval to perform a specific task 1 . It is not a method for deleting specific CIs that are not discovered in 30 days. The other options are methods for deleting or updating CIs based on discovery data.  A UI policy is a script that can dynamically change the behavior of a form or list 2 .  A service mapping is a process that creates a map of the relationships between CIs that support a business service 3 . A data policy is a rule that enforces data consistency and accuracy by validating the data entered into a record.

Debug mode is a feature of the Pattern Designer that allows you to test and troubleshoot your patterns in real time. To activate Debug mode, you need to have the admin role or a role that includes the pattern_designer_debug permission.  Debug mode is not available for users who only have the pattern_designer_read permission 1 .

In ServiceNow Discovery, a horizontal discovery pattern refers to the logical set of steps that the Discovery process executes to find CI information across the network. Each step in a horizontal discovery pattern performs specific operations such as running probes, executing commands, or querying databases to gather information about the configuration items (CIs). It's about expanding the breadth of discovery across devices and applications, rather than going in-depth into a specific CI's details, which would be vertical discovery. Classifiers, credential depots, and port scanning tools are part of the discovery process but do not describe the horizontal discovery pattern itself.

A horizontal discovery pattern is a set of steps that execute operations to identify, classify, and populate attributes for configuration items (CIs) of a specific category or class, such as infrastructure or application.  A horizontal pattern can be applied to any operating system or platform that supports the required protocols and commands 1 2 .

The $process.executableDir expression correctly calls the value of the executableDir variable from the tabular process variable. The process variable is a tabular variable that contains the output of the ps command, which lists the processes running on a CI. The executableDir variable is a column name that holds the directory path of the executable file for each process.  To access the value of a column name from a tabular variable, you need to use the dot notation, such as $variable.columnName 1 2 .

References

1 : Pattern variables - Product Documentation: Tokyo - Now Support Portal

2 : Examples of EVAL scripts used in Discovery patterns - ServiceNow