In a discovery pattern, CI Attributes are the fields that store the information about the configuration items (CIs) that are discovered by the pattern. The Pattern Designer is a graphical interface that allows users to create and edit patterns using drag-and-drop operations. In the Pattern Designer, there are two types of CI Attributes that are available: Main pattern CI type and Related CI types. The Main pattern CI type is the CI type that the pattern is designed to discover, such as Windows Server, Linux Server, or Database. The Related CI types are the CI types that are related to the main CI type, such as IP Address, Network Adapter, or Software Installation. Users can select the CI Attributes from these types to populate the CMDB tables with the data collected by the pattern123.

References:

• Patterns and horizontal discovery - Product Documentation: Tokyo - Now Support Portal
• Pattern Designer - Product Documentation: Vancouver - ServiceNow
• Discovery pattern designer - ServiceNow IT Operations Management [Book]

To troubleshoot discovery issues from a discovery status in ServiceNow, the following related lists can be particularly useful:

• Discovery Log - Provides detailed logs of the discovery process, helping to identify errors or issues encountered during discovery.
• ECC Queue - Shows the messages and data passed between the ServiceNow instance and the MID Server, offering insights into the communication and data exchange during discovery.
• Devices - Lists the devices discovered in the process, allowing for a direct view of the results and any potential issues with specific devices.

The "Running Processes" list is not typically used for troubleshooting discovery processes as it relates more to the operational aspects of the server or device rather than the discovery process itself. References = ServiceNow Discovery documentation, specifically the sections on Discovery troubleshooting and analysis, and the use of related lists for monitoring and troubleshooting purposes.

• A is true because the target table $cmdb_ci_web_server is a ServiceNow CMDB table that stores information about web servers1.
• B is true because the merge table operation is typically used for application patterns, which are horizontal patterns that discover applications and their dependencies. The condition on the process.executablePath variable suggests that the operation is looking for a specific application (mongoose) running on the web servers.
• D is true because the merge table operation requires at least one matching field value between the two source tables1. In this case, the process.executablePath variable is the matching field, and it must contain “mongoose” for the operation to run.

References:

• 1: Merge tables - Product Documentation: San Diego - Now Support Portal
• 3: Product Documentation | ServiceNow
• [4]: Discovery Patterns - Product Documentation: San Diego - Now Support Portal

The SNMP Query pattern operation executes an SNMP query on a target device and stores the results in a variable. The Variable Type field determines the format of the results. There are two valid Variable Types for this operation: Table and Scalar. Table is used when the query returns multiple values, such as a list of interfaces or processes. Scalar is used when the query returns a single value, such as the system name or uptime12.

References:

• SNMP Query pattern operation - Product Documentation: San Diego - Now Support Portal
• SNMP Query pattern operation - Product Documentation: Vancouver - ServiceNow

Horizontal discovery patterns are a series of operations that tell Discovery which CIs to find on your network, what credentials to use, and what tables to populate in the CMDB. Horizontal discovery patterns use variables to store and pass information between the operations. By default, there are two variables that are automatically available for horizontal discovery patterns: infrastructure_system and computer_system. These variables store the information about the infrastructure and the computer system of the target CI, respectively. They are populated by the Horizontal Pattern probe and sensor, which enable Discovery to use patterns for horizontal discovery123.

References:

• Patterns and horizontal discovery - Product Documentation: Tokyo - Now Support Portal
• Horizontal Pattern probe - Product Documentation: San Diego - Now Support Portal
• Using patterns for horizontal discovery - Product Documentation: Vancouver - ServiceNow

According to the ServiceNow website1, the key capabilities of a ServiceNow ITOM Enterprise solution are:

• Manage hybrid clouds: Gain visibility and control across your hybrid cloud environment with a single system of action for IT.
• Proactively eliminate service outages: Identify issues and anomalies before they cause service outages with AIOps and machine learning.
• Automate IT service operations: Automate common service requests, processes, and tasks with digital workflows and virtual agents.
• Optimize IT service delivery: Align your IT resources and investments with business priorities and optimize service delivery performance.

References:

• 1: ITOM - Enterprise IT Operations Management - ServiceNow

For a pattern operation, the <_> placeholder can be replaced by any valid index or wildcard character that can be used to access an element of an array or a table. The $IfTable variable is a table that contains information about the network interfaces of a device1. The InstanceID attribute is a unique identifier for each interface2. To access the InstanceID of a specific interface, the pattern operation can use the following syntax:

$IfTable[].InstanceID

where is either:

• A numeric index that corresponds to the position of the interface in the table, such as 3 for the third interface.
• A dot (.) followed by a key-value pair that matches a specific attribute and value of the interface, such as [.Name=eth0] for the interface with the name eth0.
• An asterisk () that represents a wildcard that matches any interface in the table, such as [] for all interfaces.

References:

• 1: IfTable - Product Documentation: San Diego - ServiceNow
• 2: InstanceID - Product Documentation: San Diego - ServiceNow

In a Merge Table pattern operation within ServiceNow Discovery, the editable fields typically include the Target Table, Second Table, and First Table. These fields are configurable and allow users to specify the tables involved in the merge operation. The Target Table is where the merged data will be stored, while the First and Second Tables are the source tables whose data is being merged. The Primary Table is not typically an editable field in this context. References = ServiceNow Discovery documentation, particularly the sections discussing pattern design and operations, including Merge Table operations within Discovery Patterns.