---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery patterns used by ITOM Visibility

# Discovery patterns used by ITOM Visibility {#ariaid-title1}

* Release version: Yokohama
* 
* Updated October 9, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Discovery patterns used by ITOM Visibility

Discovery patterns in ITOM Visibility enable ServiceNow customers to efficiently identify and map configuration items (CIs) such as network devices and applications within their IT environments.
These patterns consist of sequences of commands designed to detect CI attributes and their connections, supporting both Discovery and Service Mapping processes.
Infrastructure patterns focus on inventorying devices, while application patterns support both device inventory and detailed service instance mapping.
Show full answer Show less  
Service Mapping initiates Discovery's horizontal discovery to gather host information, which it then uses for top-down service instance mapping. Patterns are stored centrally and assigned to CI types, allowing flexible discovery of both main and related CI components, supporting diverse protocols and operating systems.

## Key Features

* **Preconfigured and Customizable Patterns:** ServiceNow provides a comprehensive library of patterns covering standard industry devices and applications, which can be customized or extended to accommodate proprietary or modified CIs.
* **Pattern Types:** Infrastructure patterns create device inventories; application patterns facilitate both inventory and detailed service mapping.
* **Pattern Versioning and Management:** Customized patterns are maintained separately from original versions, allowing updates from the ServiceNow Store without overwriting customizations. Customers can revert to original patterns as needed.
* **Domain Separation Support:** Patterns can be global or domain-specific, allowing tailored discovery in multi-domain environments.
* **Role-Based Access:** Specific user roles control pattern creation, editing, publishing, and viewing, ensuring controlled management of discovery logic.
* **Integration with MID Server:** MID Servers execute pattern-based probes, enabling discovery across network boundaries.
* **Pattern Creation Workflow:** Patterns are typically developed and tested in a development instance before being deployed to production via update sets.
* **Entry Point Types for Service Mapping:** Predefined and customizable entry points enable accurate mapping start points for application services.
* **Enhancements and Extensions:** Extension sections within patterns allow adding discovery logic without modifying core identification, facilitating maintenance and enhancements.
* **Performance Improvements:** Direct population of key fields in CI tables and optimized server CI population reduce discovery time and improve query efficiency.
* **Authentication Support:** Oracle Wallet authentication can be enabled for secure discovery of Oracle databases on UNIX systems.

## Practical Benefits and Outcomes

* **Comprehensive Visibility:** Out-of-the-box patterns provide extensive coverage of industry-standard devices and applications, enabling rapid and accurate discovery.
* **Customization Flexibility:** Customers can create or adapt patterns to match unique environments, ensuring all relevant CIs are discovered and accurately represented.
* **Consistent and Controlled Updates:** Pattern versioning and management ensure that updates do not disrupt customized discovery logic, maintaining stability and reliability.
* **Effective Service Mapping:** Integration of horizontal discovery data allows Service Mapping to build detailed service instance maps, improving service understanding and impact analysis.
* **Domain-Aware Discovery:** Support for global and domain-specific patterns facilitates discovery in complex, multi-domain organizations.
* **Enhanced Discovery Efficiency:** Performance optimizations and authentication mechanisms reduce discovery duration and improve security.  
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 {#c_MappingPatternsCustomization__section_pvt_gnb_wz}

A pattern is a sequence of commands whose purpose it is 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.
{#c_MappingPatternsCustomization__table_jt1_wpv_rw__entry__3}

| Product | Pattern type | Result |
|-|-|-|
| Discovery | Infrastructure pattern | Inventory list of devices |
| Discovery | Application pattern | Inventory list of applications |
| Service Mapping | Application pattern | Service instance map |
[Table 1. Pattern usage by Service Mapping and Discovery]

{#c_MappingPatternsCustomization__table_jt1_wpv_rw}

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](https://servicenow-prod.fluidtopics.net/0t85gIX3hGiF4CP5GDz2Cg "The horizontal discovery process passes through the four phases of discovery using probes, which gather information on the target machine, and then sensors, which help Discovery determine what to do with that information.").

## Correlation between pattern and CI type {#c_MappingPatternsCustomization__section_dp3_z4b_wz}

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. Figure 1. Main CI type discovery during top-down discovery   

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. Figure 2. Discovery of main and related CI types during horizontal discovery   

## Why install patterns from the ServiceNow Store {#c_MappingPatternsCustomization__section_zlm_vfx_r3b}

ServiceNow releases new discovery patterns on the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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 {#c_MappingPatternsCustomization__section_fml_mnb_wz}

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.
{#c_MappingPatternsCustomization__ul_awx_lt3_b5}

## Pattern versions {#c_MappingPatternsCustomization__section_n2v_xpb_wz}

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.
Figure 3. Exclusion of a customized pattern from an upgrade   

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](https://servicenow-prod.fluidtopics.net/MzEXI3G4~iDw5iojKTLLnA "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.").

## Patterns users {#c_MappingPatternsCustomization__section_jyt_xss_5gc}

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.  
{#c_MappingPatternsCustomization__table_pg3_4ts_5gc__entry__2}

| 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: * Command List \[pd_command_list\] * Command Validation Task \[pd_command_validation\] * Command Validation Task Results \[pd_command_validation_results\] * Pattern Shared Library Mapping \[pd_pattern_to_shared_library_mapping\] * Temporary Variable Mappings \[pd_temp_variable_value_mapping\] {#c_MappingPatternsCustomization__ul_i54_bx2_ghc}For more information, see [Discovery commands for probes and patterns](https://servicenow-prod.fluidtopics.net/ATbmi05od6rcXEGKXzCwZw "Discovery commands are used for both probe and pattern-based discovery to access configuration items (CIs) in your environment."). |
| 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. |
[Table 2. Patterns users and access]

{#c_MappingPatternsCustomization__table_pg3_4ts_5gc}

## Patterns for instances using domain separation {#c_MappingPatternsCustomization__section_cgr_cxb_wz}

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.Figure 4. Global or domain-specific patterns   

## Pattern creation or modification flow {#c_MappingPatternsCustomization__section_gzv_2pb_wz}

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.
Figure 5. Pattern creation flow   

1. [Available discovery patterns](https://servicenow-prod.fluidtopics.net/apXXo5Qg1EKex2K~T9~EaQ)  
   ITOM Visibility comes with an extensive library of patterns.
2. [Configuring Pattern Designer and related applications](https://servicenow-prod.fluidtopics.net/_Dr6ziAU0NcGN48L8Gn~AA)  
   Install the latest available versions of the ServiceNow applications to use the latest discovery patterns.
3. [Create CI types for Service Mapping and Discovery](https://servicenow-prod.fluidtopics.net/e4PiqLRzZadXLjV7QE7X5Q)  
   Create CI types (or CI classes) for applications and devices, which Service Mapping and Discovery do not support by default.
4. [Create entry point types for Service Mapping](https://servicenow-prod.fluidtopics.net/I8a_fpSTDrjMoM5zjF3YIw)  
   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.
5. [Create or customize patterns](https://servicenow-prod.fluidtopics.net/ZaWnPMmnvybQ8YI3j0l7LA)  
   Create or modify a discovery pattern and define its basic attributes.
6. [Discover related items together with the main CI](https://servicenow-prod.fluidtopics.net/P7~pCne5ETsQymLENF70iw)  
   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.
7. [Enhance patterns without modifying identification sections](https://servicenow-prod.fluidtopics.net/PwiiodQjpq1vI05SDNR6Sg)  
   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.
8. [Fine-tune patterns using traffic-based discovery](https://servicenow-prod.fluidtopics.net/UkfXq4ukdyThEwNF7wIkQg)  
   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.
9. [Finalize a pattern](https://servicenow-prod.fluidtopics.net/XLimhp~f0lPKENldSoCZ~w)  
   After you finish defining your pattern, make it ready for use by Service Mapping and Discovery.
10. [Copy patterns from one instance to another](https://servicenow-prod.fluidtopics.net/lRYzAqYCw2FGygy3SHeYEg)  
    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.
11. [Choose the pattern version](https://servicenow-prod.fluidtopics.net/MzEXI3G4~iDw5iojKTLLnA)  
    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.
12. [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw)  
    If you want to use a pattern for discovery that's disabled by default, activate it manually.
13. [Improved query performance with direct field population in CI tables](https://servicenow-prod.fluidtopics.net/H_wfVmrRA2K_BT9VRkb6iQ)  
    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.
14. [Server CI population during cloud discovery](https://servicenow-prod.fluidtopics.net/l3F5FpeIB1umNnVxXqBEHg)  
    Cloud discovery can populate Server CIs without running IP-based discovery, reducing discovery time in large environments.
15. [Enable Oracle Wallet authentication for discovery](https://servicenow-prod.fluidtopics.net/m3ylp7_~xsnVF9p_jzBBdg)  
    Enable Oracle Wallet authentication to use credentials stored on the target server during Oracle database discovery on UNIX systems.

**Related concepts**   

* [Application patterns for the Agent Client Collector](https://servicenow-prod.fluidtopics.net/ga~C7dH8i6LRLDLN3_CjrQ "Application patterns gather details on the applications that run on the Agent Client Collector (ACC) host. Application patterns are supported only for servers, and are triggered after the Agent Client Collector host Discovery is complete.")  
**Related reference**   

* [Detailed information on products discovered by ITOM Visibility](https://servicenow-prod.fluidtopics.net/AB0jKyDtjf78iS3uAPUKpg "Discovery and Service Mapping can discover a wide range of operating systems and applications.")
* [Certificate Inventory and Management patterns](https://servicenow-prod.fluidtopics.net/S6XrKVG25GzieYc_U3Z69A "Efficiently manage your Certificate Inventory with patterns to streamline the management of digital certificates. Patterns reduce the risk of vulnerabilities by bolstering security, compliance, and efficient lifecycle control.")  
**Related topics**   

* [Class diagrams and class attributes for key CMDB classes](https://www.servicenow.com/docs/access?context=c_ConfigurationManagementDatabase&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [Description of key CMDB tables in the base system](https://www.servicenow.com/docs/access?context=cmdb-tables-details&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [CMDB CI Class Models: ServiceNow Store app that adds class models that extend the
  base CMDB class hierarchy](https://www.servicenow.com/docs/access?context=cmdb-ci-class-models&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [Information about the various options for populating the CMDB](https://www.servicenow.com/docs/access?context=c_OptionsToPopulateCMDB&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [ServiceNow Store apps that provide pre-defined Service Graph connectors for
  importing and integrating common third-party data into CMDB classes](https://www.servicenow.com/docs/access?context=cmdb-third-party-integrations&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [KB0747679: Pre/Post Processing Scripts for patterns](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0747679)