---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Exploring Discovery

# Exploring Discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Exploring Discovery

Discovery in ServiceNow identifies computers, servers, printers, various IP-enabled devices, and the applications running on them.
It updates the Configuration Management Database (CMDB) with accurate configuration item (CI) data.
Discovery supports two complementary approaches: horizontal discovery and top-down discovery, often used together to provide a comprehensive view of your IT environment and business services.
Show full answer Show less  

## Types of Discovery

* **Horizontal Discovery:** Scans networks to find devices and applications, populating the CMDB with these CIs and their direct relationships (e.g., an application running on a server). It does not map business service dependencies.
* **Top-down Discovery (Service Mapping):** Maps CIs within business services, showing dependencies such as between web servers and databases, providing insights into service relationships.

## Key Components

* **Probes and Sensors:** Probes collect data from devices; sensors parse this data to update the CMDB. These can be customized or created to gather specific information.
* **Patterns:** Written in Nebula Discovery Language (NDL), patterns perform complex discovery operations during later horizontal discovery phases. They can be customized or created using the Pattern Designer.
* **MID Server:** Executes probes and patterns securely within your network, initiating all communications from inside the firewall without requiring agents on devices.

## Horizontal Discovery Phases

* **Scanning:** Sends the Shazzam probe to detect open ports and identify device types.
* **Classification:** Uses additional probes to determine device types and operating systems, triggering classifiers that guide subsequent discovery steps.
* **Identification:** Gathers detailed information to find or create corresponding CIs in the CMDB, using identification rules to reconcile data.
* **Exploration:** Collects extended attributes and application details, establishing relationships between devices and applications.

## Types of Horizontal Discovery

* **Network Discovery:** Identifies internal IP networks.
* **CI Discovery:** The standard discovery to find devices, computers, and applications.
* **Cloud Discovery:** Discovers AWS and Azure cloud resources.
* **Serverless Discovery:** Finds applications on hosts without discovering the host first, relying on patterns.

## IP Service Affinity

This feature records the successful IP protocol used to discover a device and associates it with the device's IP address. It optimizes future discovery runs by prioritizing the correct protocol (e.g., SNMP over SSH for network devices), improving discovery efficiency and accuracy.

## Practical Benefits for ServiceNow Customers

* Enables automated, agentless discovery and CMDB population, reducing manual effort and errors.
* Provides a clear and accurate inventory of IT infrastructure and application relationships.
* Supports integrated service mapping to visualize business service dependencies.
* Offers customization options through probes, sensors, and patterns to tailor discovery to specific environments.
* Ensures secure and efficient discovery operations via MID Servers without complex firewall or VPN configurations.  
Discovery finds computers, servers, printers, a variety of IP-enabled devices, and the applications that run on them. It can then update the configuration items (CIs) in your Configuration Management Database (CMDB) with the data it collects.

## Horizontal discovery and top-down discovery {#c_GetStartedWithDiscovery__section_bfk_n1g_ycb}

There are two types of discovery:

Horizontal discovery

:   Horizontal discovery is a technique that Discovery uses to scan your network, find computers and devices, and then populate the CMDB with the CIs it finds. Horizontal discovery creates direct relationships between CIs, such as a `runs on` relationship between an application CI and the
    actual computer CI that it runs on. Horizontal discovery is not aware of business services and does not create relationships between CIs based on the business service they are in.

Top-down discovery

:   Top-down discovery is a technique that Service Mapping uses to find and maps CIs that are part of business services, such as an email service. For example, top-down discovery can map a website business service by showing the
    relationships between an Apache
    Tomcat web server service, a Windows server, and the MSSQL database. This gives IT teams a clear view of service dependencies.

    Typically, Service Mapping and Discovery work together. Horizontal discovery runs first to find CIs, and then top-down discovery establishes the relationships between business services.

## Probes, sensors, and patterns {#c_GetStartedWithDiscovery__section_xqk_wlt_jkb}

Discovery uses these components to find CIs:

[Probes and sensors](https://www.servicenow.com/docs/Af~VFnWMDR7QiImX9LEh7Q "The horizontal discovery process passes through the four phases of discovery using probes, which gather information on the target machine. Sensors then help Discovery determine what to do with that information.")
:   Probes and sensors are scripts that collect and process data on a host and then update the CMDB. More specifically, probes explore or investigate CIs on your network, and sensors parse the data returned from the probes. Several probes and sensors are provided by
    default, but you can customize them to find different information, or you can create ones. You can also configure several parameters to control the behavior of a particular probe every time it is triggered.

[Patterns](https://www.servicenow.com/docs/SotY1kbxGXkCxDgjjGC1lA "Horizontal discovery with patterns has four phases, just as horizontal discovery with probes does. However, for the last two phases, Discovery triggers operations from a pattern, rather than additional sets of probes.")
:   Patterns, like probes and sensors, are a series of operations that also collect data on a host, process it, and update the CMDB. Patterns differ from probes and sensors in that they are written in Neebula Discovery Language (NDL) rather than JavaScript. They are called into action in the later stages of the horizontal discovery process. Default patterns are provided, but you can also customize or
    create patterns using the Pattern Designer.

## Horizontal discovery phases {#c_GetStartedWithDiscovery__discovery-phases}

The phases of horizontal discovery are:  
Discovery follows these phases:

Scanning
:   Discovery sends a probe called Shazzam to the network to see if commonly used ports are open
    and if these ports can respond to queries. For example, if Shazzam finds a device that responds on port 135, Discovery knows that it's a Windows server.

Classification
:   If Discovery finds devices or computers, it sends additional probes to find the type of device or the
    operating system on the device. For example, Discovery sends the WMI probe to a Windows machine to detect the Windows 2012 operating system. Then Discovery uses records called classifiers, which specify the trigger probe or probes that run
    during the next two phases. If you're using patterns, the classifier specifies a trigger probe that in turn launches a pattern.

Identification
:   Discovery tries to gather more information about the device and then tries to determine if a CI for the
    device exists in the CMDB. Discovery then uses additional probes, sensors, and identifiers to update existing CIs in the CMDB or
    create new ones. Identifiers, also known as identification rules, specify the attributes that the probes look at when reconciling data with the CIs in the CMDB. If you're using patterns, Discovery uses the appropriate identification rule for the CI type specified in the pattern.

Exploration
:   The identifier launches additional probes configured in the classifier. These probes gather additional information about the device, including the applications running on it and attributes such as memory, network cards, and drivers. Discovery then creates relationships between applications and devices and between applications. If you're
    using patterns, the operations in the pattern perform the exploration of the CI.

## Discovery communication through MID Servers {#c_GetStartedWithDiscovery__section_lb1_fdl_f2b}

A [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US), which constantly queries the instance for probes to run, executes the instructions in the probe or in the pattern that the probe specifies. The MID Server then returns the results to the instance, where sensors process it. The MID Server does not retain any discovery information.

The MID Server starts all communications, using SOAP on HTTPS, which means that all communications are secure, and all communications are initiated inside the enterprise's firewall. No special firewall rules or
VPNs are required.

Because Discovery is agentless, it does not require any permanent software to be installed on any computer or device. The MID Server uses several techniques to probe devices without using agents. For example, the MID Server uses SSH to connect to a Unix or Linux computer. It then runs a standard command, as specified in the probe, to gather information. Similarly, it uses the Simple Network Management Protocol (SNMP) to gather information from a network switch or
a printer.

## Types of discovery {#c_GetStartedWithDiscovery__section_lvj_5gl_f2b}

The types of horizontal discovery that the Discovery application can perform are
explained in the following table:  
{#c_GetStartedWithDiscovery__table_b2w_1hl_f2b__entry__2}

| Type | Description |
|-|-|
| Network discovery | Run this type of discovery to find the internal IP networks within your organization. If you already know the IP address ranges in your network, it is not necessary to run network discovery. |
| CI discovery | Run this type of discovery to find the devices, computers, and applications on your network. This is essentially the standard type of discovery that you run most often. |
| Cloud discovery | Run this type of discovery to find AWS and Azure resources in your organization's cloud. |
| Serverless discovery | Run this type of discovery to find applications on host machines without the need to discover the host first. Serverless discovery relies on patterns to explore CIs on a host. |
[ ]

{#c_GetStartedWithDiscovery__table_b2w_1hl_f2b}

## IP service affinity {#c_GetStartedWithDiscovery__section_rwp_y3v_5bb}

IP Service affinity saves the IP service information that is used to successfully find a
device and associates it with the IP address of the device. Using this information, Discovery can target the device in
subsequent runs with the accurate protocol. Discovery records the IP Service along
with the IP address. Discovery can
store the successful IP service information in the IP Service Affinity table
\[ip_service_affinity\].

For example: A network device has both an SSH port and an SNMP port open. By its agentless
design, Discovery tries SSH first.
However, network devices should be discovered through SNMP. Discovery tries the SSH probe and it
fails. This triggers the SNMP probe, which succeeds. With the association between the IP
address and the IP service, subsequent discovery runs targeting this IP address use SNMP
first, because that is the probe that succeeded.
* **[Horizontal discovery process flow with probes and sensors](https://www.servicenow.com/docs/Af~VFnWMDR7QiImX9LEh7Q)**   
  The horizontal discovery process passes through the four phases of discovery using probes, which gather information on the target machine. Sensors then help Discovery determine what to do with that information.
* **[Horizontal discovery process flow with patterns](https://www.servicenow.com/docs/SotY1kbxGXkCxDgjjGC1lA)**   
  Horizontal discovery with patterns has four phases, just as horizontal discovery with probes does. However, for the last two phases, Discovery triggers operations from a pattern, rather than additional sets of probes.

**Related concepts**   

* [Discovery setup](https://www.servicenow.com/docs/Wo6baweD9AR0rxtzZPqfgg "After you activate the Discovery application, you have several ways to get started.")
* [Discovery monitoring and issue resolution](https://www.servicenow.com/docs/bIw207qhAFcoy2bexyhIrA "Learn how to monitor the progress of your discoveries and how to configure the system to aggregate performance metrics that are important to you. Find descriptions of the error messages you see, and possible steps you can take to solve problems. The Now Support Knowledge Base on Hi contains several articles to help you troubleshoot discovery issues.")

