---
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


---

# Configure Discovery identity sensors

# Configure Discovery identity sensors {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

If you customize an identify multi-probe, you can also configure a multi-sensor for
it.

## Before you begin

Role required: discovery_admin or admin

## About this task

These multi-sensors pass the data returned by the identity probes to the Discovery identifiers. The
identifiers then search the CMDB for matching CIs. When the identity of a device is
resolved, the identifiers pass the result state for the device to the multi-sensors,
which react accordingly, either by launching exploration probes or stopping Discovery for that device.

## Procedure

1. Navigate to AllDiscovery DefinitionSensors.
2. Select an existing identity multi-sensors from the list.  
   Note:  
   To avoid confusion, the multi-sensors provided in the instance must have the same names as their matching multi-probes.  
   The Responds to Probes related list shows the simple
   probes which pass their data to this multi-sensors. These are the same
   simple probes that appear in the Includes Probes list in the matching
   multi-probes record.
3. Click the Script link for each probe in the list to see the script that the multi-sensors runs to process the data from the probe.

## Example

Figure 1. Discovery identity sensors

## What to do next

Run a discovery through the [Discovery
Schedule](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.") to search for CIs and verify that they are identified correctly in the CMDB.

*[\>]: and then