Discovery probes and sensors

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    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 probes and sensors

    Discovery probes and sensors are integral components of ServiceNow Discovery that collect data and update the Configuration Management Database (CMDB). While newer releases increasingly use patterns to replace many probes and sensors, probes and sensors remain relevant for customers not yet using patterns or who maintain customized probes after upgrades. Probes and sensors function primarily in the scanning and classification phases of Discovery, with options to continue using them or switch to patterns in later phases.

    Show full answer Show less

    How Probes and Sensors Operate

    The MID Server manages communication via the ECC queue, monitoring and executing probes based on queued instructions. Probes gather data from devices and send it to sensors for processing. Depending on configuration, some data processing may occur on the MID Server via post-processing scripts before transmission. Sensors then process the data and update the CMDB accordingly.

    Multi-probes and multi-sensors allow grouping of multiple probes and their corresponding processing scripts to handle complex data collection efficiently.

    Probe Types and Use Cases

    • Windows computers and servers: Remote WMI queries and shell commands
    • UNIX and Linux servers: Shell commands via SSH (Bourne-compatible shells supported)
    • Storage devices: CIM/WBEM queries
    • Printers, network gear, UPS: SNMP queries
    • Web servers: HTTP header examination

    Management and Customization

    ServiceNow provides a broad range of out-of-the-box probes and sensors, which typically require little modification. Customers may need to adjust parameters or align customized probes and sensors with new versions after system upgrades. Multiprobes and multisensors enable executing multiple queries with a single authentication to streamline data gathering on manageable devices.

    A practical example includes a custom probe and sensor designed to read values from a text file on a Windows computer and populate a CI in the CMDB with those values.

    Key Considerations for ServiceNow Customers

    • Evaluate whether to continue using probes and sensors or migrate to patterns to leverage newer Discovery features.
    • Understand the role of the ECC queue and MID Server in coordinating probe execution and data processing.
    • Customize probes cautiously and ensure versions are aligned after upgrades to maintain Discovery functionality.
    • Use multiprobes and multisensors to optimize discovery performance when collecting complex or multiple data points.

    Discovery probes and sensors perform data collection and update the Configuration Management Database (CMDB).

    With each release, patterns are replacing many probes and sensors for Discovery. Consider creating new patterns or editing existing ones if you want to customize what Discovery can find. The information on probes and sensors is intended for customers who are not using patterns yet and for customers who already have customized probes that are retained upon upgrade. See Patterns and horizontal discovery for more information on patterns.

    Note:
    For information on Probe to Pattern migration see the knowledge article KB0694477.

    Discovery phases

    Discovery always uses probes and sensors during the first two phases of discovery: scanning and classification. For the last two phases, identification and exploration, Discovery can use probes and sensors or patterns. This topic refers to probes and sensors only. See Exploring Discovery for an explanation of these phases. See Patterns and horizontal discovery for more information on patterns.

    Probes, sensors, and the ECC queue

    The probe collects the information and the sensor processes it. Both get their instructions from the ECC queue. There is a worker job on the MID Server that monitors the queue for work. The monitor checks for any entries where the Queue is output and the State is ready.
    The ECC queue
    The MID Server then processes all the output ECC messages, runs the necessary probes, and returns the probes results to the ECC queue. These results are put in the ECC Queue as input entries.
    Figure 1. ECC queue input
    ECC queue record

    After an entry is inserted in the ECC Queue table, a business rule fires (on insert) that takes that information and runs it through a sensor processor. The sensor processor's job is to take the input data, find any sensors interested in that data, and pass it along to be processed. Those sensors ultimately update the CMDB.

    How probes and sensors work together

    The MID Server launches probes to collect information about a device. The probe sends back information to the sensor to be processed. If the probe has a post-processing script defined, the post-processing script does some data processing on the MID Server before data is sent back to the sensor on the ServiceNow instance. Otherwise the probes sends back all the data collected and the sensor performs this data processing. In both cases, the sensor updates the CMDB.

    A multi-probe is a probe that contains probes. A multi-sensor processes the data from a multi-probe. To process the data from the multi-probe, the multi-sensor contains individual scripts to process the data returned by each probe contained in the Multiprobe, as well as a main multi-sensor script. The individual scripts pass their processed data to the main multi-sensor script.

    The MultiSensor form

    Probe types

    Device Probe Type

    Windows

    computers and servers
    Remote WMI queries, shell commands

    UNIX and Linux servers

    Shell command (via SSH protocol, version 2). Discovery supports any Bourne-compatible shell.

    Storage CIM/WBEM queries
    Printers SNMP queries
    Network gear (switches, routers, etc.) SNMP queries
    Web servers HTTP header examination
    Uninterruptible Power Supplies (UPS) SNMP queries