Discovery patterns used by ITOM Visibility
Service Mapping and Discovery use patterns in their discovery process that cover most industry standard network devices and applications. You can customize these patterns and create new ones.
ServiceNow applications refer to devices and applications that comprise a service instance as configuration items (CIs).
What discovery patterns are
A pattern is a sequence of commands designed to detect attributes of a CI and its outbound connections. Service Mapping and Discovery share a set of preconfigured patterns that cover most of the commonly used devices and applications. Patterns can be of the infrastructure or application type. Infrastructure patterns are used only by Discovery for creating lists of devices. Application patterns serve both Service Mapping and Discovery, which use the same application patterns for their purposes. For example, Discovery runs the horizontal discovery with the Apache Web Server pattern to find and list all Apache Web Servers in your organization. Service Mapping runs the top-down discovery using the same pattern to discover a specific Apache Web Server and place it on a service instance map.
Note: Currently, pattern operations do not support multi-languages. If values returned from pattern operations are not in English, the returned data cannot be parsed properly and the pattern discovery will fail.
| Product | Pattern type | Result |
|---|---|---|
| Discovery | Infrastructure pattern | Inventory list of devices |
| Application pattern | Inventory list of applications | |
| Service Mapping | Application pattern | Service instance map |
For discovering devices that act as hosts for applications, Service Mapping relies on Discovery. As part of the top-down discovery process, Service Mapping triggers Discovery to perform its horizontal discovery behind the scenes. Service Mapping then uses information on hosts provided by the horizontal discovery to create its service instance maps.
Patterns of all types are stored in the Discovery Patterns [sa_pattern] table.
Discovery uses a combination of probes and patterns. For more information, see Horizontal discovery process flow with probes and sensors.
Correlation between pattern and CI type
Patterns are assigned to the CI types that they serve to discover. If necessary, you can assign more than one CI type per pattern. In that case, you define one main CI type and multiple related CI types. For example, a pattern for discovering BIG-IP Global Traffic Manager (GTM) F5 has F5 BigIP GTM as its main CI type. It also has related CI types for the Domain Name System (DNS) name, network adapter, and other components.
For the top-down discovery performed by Service Mapping, each application pattern serves to discover only the main CI type.
During top-down discovery, a pattern discovers only the main CI type.
However, Service Mapping usually uses more than one pattern to discover the same CI type, because a CI type can use different protocols, operating systems, entry points, and so on.
Unlike top-down discovery, the process of horizontal discovery uses each pattern to discover a main CI type with all related CI types.
During horizontal discovery, a pattern discovers the main CI type and all related CI types.
Why install patterns from the ServiceNow Store
ServiceNow releases new discovery patterns on the ServiceNow Store on a monthly basis to ensure that your organization can discover the latest industry-standard devices and applications. Major ServiceNow versions incorporate patterns previously released on the ServiceNow Store.
ServiceNow releases all discovery patterns using the following applications:
Discovery and Service Mapping Patterns (sn_itom_pattern)
This application provides the latest versions of discovery patterns the original version of which ServiceNow released on ServiceNow Store.
Visibility Content (sn_pattern_design)
This application supplies the updated version of the patterns that were part of the family releases up until Tokyo.
You can install the latest available versions of the pattern applications from the ServiceNow Store. Alternatively, you can install these applications as plugins on your ServiceNow instance.
Why customize patterns
You can customize patterns in the following cases:
- If your organization uses proprietary devices and applications, create patterns for these items to enable Discovery and Service Mapping to discover them.
- If you modify key attributes of CI types that had corresponding patterns, modify the relevant patterns to reflect the change.
Pattern versions
When you customize a pattern, you actually create a copy of the original preconfigured pattern. While Service Mapping or Discovery use the customized version, the original version isn’t deleted. When you download an update of the pattern from the ServiceNow Store, the original pattern is updated, not the customized copy of it.
A customized copy of a pattern is not updated.
If at some point you want to abandon the customized pattern and start using the updated original pattern, you can revert to the original pattern as described in Choose the pattern version.
Patterns users
The following user roles have access to patterns or pattern-related modules and can perform various actions. Note that customizing patterns requires basic knowledge of programming.
| User | Description |
|---|---|
| Discovery admin | Can view, create, edit, and publish patterns. The role enables users to run discovery, migrate probes or CAPI to patterns, and access discovery logs and dashboards. |
| PD user | Has read-only access to Discovery Pattern Log. |
| PD admin | Can view, create, edit, and publish patterns. |
| PDE viewer | Starting with Pattern Designer Enhancements version 3.9.0, users can view Command Validation Tasks, Command Validation Tasks Results, and Command List. The pde_viewer can view the Command Validation Tool modules and related tables, but doesn't have permissions to modify or edit them. The pde_viewer role can view the following tables only:
For more information, see Discovery commands for probes and patterns. |
| PD MID | Not assigned to a user directly but to the MID Server record or the user under which the MID Server runs. The role enables the MID Server to interpret and run pattern-based probes. |
| MID Server | Can grant the MID Server access to the instance. |
Patterns for instances using domain separation
In instances that use domain separation, patterns might be domain-specific, covering only the domains that you created them for, or global, applying to all domains.
Patterns belong to domains. By default, all preconfigured patterns are assigned to the global domain and apply to all domains of all levels.
You can create patterns for specific domains. In that case, the new pattern is used only for this domain and doesn’t exist in any other domains. If you customize an existing pattern in the global domain and assign it to a specific domain, you create a copy of the global pattern. The original global pattern is still used for all other domains except for the domain that has the customized version of this pattern. Likewise, if you customize the pattern belonging to the global domain, the change affects all domains except for the one that uses a customized copy of this pattern.
Patterns may be domain-specific or global.
Pattern creation or modification flow
Typically, you maintain two ServiceNow instances in your organization: for production and for development. Create or modify patterns, test them, and verify results in the development instance. When you are satisfied with the discovery results, export relevant patterns from the development instance to create an update set. Then you retrieve and commit the update set in your production instance.
If you’re creating a pattern for applications and devices that aren’t supported in the ITOM Visibility global content application, start from creating CI types for them.
Flow describing pattern creation and modification
- Available on-premise discovery patterns
ITOM Visibility comes with an extensive library of patterns. - Available cloud discovery patterns
ITOM Visibility comes with an extensive library of patterns that can discover your cloud environment: AWS, Azure, GCP, IBM, and OCI. - Configuring Pattern Designer and related applications
Install the latest available versions of the ServiceNow applications to use the latest discovery patterns. - Create CI types for Service Mapping and Discovery
Create CI types (or CI classes) for applications and devices, which Service Mapping and Discovery do not support by default. - Create entry point types for Service Mapping
An entry point is a point where clients access a service instance. Service Mapping starts the mapping process for every application service from the entry point you define for it. Service Mapping includes a wide range of preconfigured entry point types that cover most commonly used applications. If your organization uses a less known or proprietary application that does not have a corresponding entry point type in Service Mapping, you must create it. - Create or customize patterns
Create or modify a discovery pattern and define its basic attributes. - Discover related items together with the main CI
Add related items to the patterns to perform horizontal discovery of configuration items with all their related items: CIs or non-CIs, like ports or serial numbers. - Enhance patterns without modifying identification sections
Enable patterns to search for additional attributes and modify pattern discovery logic defined in identification sections by using extension sections. Each extension section contains a preconfigured set of discovery steps referred to as a shared library. - Fine-tune patterns using traffic-based discovery
As an alternative to customizing the pattern from the Pattern Designer side, improve existing patterns so that Service Mapping can use them to find configuration item (CI) connections previously found using traffic-based discovery. - Finalize a pattern
After you finish defining your pattern, make it ready for use by Service Mapping and Discovery. - Copy patterns from one instance to another
To copy patterns from one instance to another, create an update set containing new or modified patterns with their related items in your development instance. Then, import the update set into your production instance. - Choose the pattern version
Every time you modify and save a pattern, you create a version of this pattern. Choose which pattern version Service Mapping and Discovery use for discovery. - Activate a disabled pattern
If you want to use a pattern for discovery that's disabled by default, activate it manually. - Discover datacenters only for new cloud accounts
If you have multiple cloud accounts and datacenters in AWS and Azure, you can discover datacenters for new cloud accounts only, instead of refreshing the entire list. - Improved query performance with direct field population in CI tables
The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance. - Server CI population during cloud discovery
Cloud discovery can populate Server CIs without running IP-based discovery, reducing discovery time in large environments. - Enable Oracle Wallet authentication for discovery
Enable Oracle Wallet authentication to use credentials stored on the target server during Oracle database discovery on UNIX systems.
Parent Topic:ITOM Visibility
Related topics
Detailed information on products discovered by ITOM Visibility
Class diagrams and class attributes for key CMDB classes
Description of key CMDB tables in the base system
Information about the various options for populating the CMDB
KB0747679: Pre/Post Processing Scripts for patterns