---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Horizontal discovery process flow with probes and sensors

# Horizontal discovery process flow with probes and sensors {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

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.

## Kicking off Discovery

A user triggers horizontal discovery by configuring a discovery schedule or by launching an on-demand discovery with Discover now or Quick Discovery. The schedule specifies one or more IP addresses or
range of IP addresses.

## Scanning phase

1. Discovery first takes the Shazzam probe (and then [port probes](https://servicenow-prod.fluidtopics.net/sEH6sQnBbOcdpeAGeA8WtQ "Port probes are used in Discovery by the Shazzam probe to detect protocol activity on open ports on devices it encounters.")) and places it in a request in the External Communication Channel (ECC) queue.
2. The MID Server checks the ECC queue, retrieves the discovery request, and runs the probes against the host and discovers open ports.
3. The port probes scan common ports using several protocols, such as WMI, HTTP, SSH, and SNMP.
4. If one or more ports respond, the Shazzam probe sends information about the port back to the ECC queue through the MID Server.
5. Discovery checks the ECC queue to find out which ports responded, which identifies the type of machine. For example, if Shazzam detects that the machine is listening on port 22, Discovery treats the machine as a UNIX or Linux machine.
{#c_DiscoProcessFlows__ol_m13_l45_bz}

## Classification phase

1. The Discovery application determines which classification probe to send to the newly discovered device by using information in the record of the port probe that successfully responded.
2. Discovery puts the classification probe into the ECC queue.
3. The MID Server checks the ECC queue, retrieves the discovery request, and runs the classification probe.
4. The classification probe retrieves additional information, such as which version of the operating system is running on a machine. This information determines the class of the CI that Discovery found. There is only one classification probe per discovered device.
5. The classification probe sends information back to the instance ECC queue through the MID Server.
{#c_DiscoProcessFlows__ol_ey2_pqt_lx}

## The Identification phase

1. Discovery determines which classifier to use based on the class of the CI and the criteria specified in all CI classifier records. The classifier specifies which probes to use for the next two phases.
2. Discovery puts the identification trigger probe for the CI classifier into the ECC queue. For example, a UNIX machine running HP-UX would require the HP-UX classifier, which specifies that the Multi Probe-HP-UX Identity identification trigger probe. These probes use identification rules to determine whether or not to insert or update a CI in the CMDB.  
   Hinweis:  
   The trigger probe could also be the Horizontal Pattern probe, which tells Discovery to follow the operations in the specified pattern, rather than sending out additional probes. The operations in the pattern cover both the identification and exploration phases. Discovery knows which identification rules to use based on the CI type, and Discovery makes inserts or updates to the CMDB based on these rules. Probes and sensors are not used.
3. The MID Server checks the ECC queue, retrieves the discovery request, and runs the identification trigger probe.
4. The identification probe accumulates identification data for each device and sends that data back to the instance via the MID Server.
5. Discovery uses sensors for the identifier probe to process the information.
6. Discovery performs the analysis on the CMDB using [CI identifiers](https://servicenow-prod.fluidtopics.net/~dEYPW7lMymcGfXoKnPQUQ "After Discovery classifies a CI, it uses identifiers to determine if the device already exists in the CMDB."). Discovery can update existing CIs in the CMDB or create new ones.
{#c_DiscoProcessFlows__ol_thp_zst_lx}

## The Exploration phase

1. Discovery looks at the Triggers Probes related list in the classifier to find exploration probes to run.
2. Discovery puts the exploration trigger probe into the ECC queue.
3. The MID Server checks the ECC queue, retrieves the discovery request, and runs the exploration trigger probes.
4. The probes send data back to the instance via the MID Server and sensors make updates to the CMDB, just as in the identification phase.
{#c_DiscoProcessFlows__ol_y3p_445_bz}
**Zugehörige Konzepte**   

* [Horizontal discovery process flow with patterns](https://servicenow-prod.fluidtopics.net/V8kBP_ufS_1GJm~dcxlfog "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 and horizontal discovery](https://servicenow-prod.fluidtopics.net/lq7dwcGPzgHCi~AZFOJBIA#c-UsingPatternsForHorizontalDiscovery "A pattern is 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.")