Discovery probes and sensors

  • Release version: Yokohama
  • Updated January 30, 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 essential components in ServiceNow Discovery that collect data and update the Configuration Management Database (CMDB). While newer releases increasingly favor patterns over probes and sensors, many customers still use or customize probes. Probes gather information from devices during discovery, and sensors process this data to update the CMDB.

    Show full answer Show less

    Discovery uses probes and sensors primarily in the scanning and classification phases, and optionally in the identification and exploration phases. Probes run on the MID Server, which monitors the ECC queue for work instructions and returns collected data for processing.

    How Probes and Sensors Work Together

    The MID Server launches probes to collect device information. Probes may run post-processing scripts on the MID Server before sending data back. Sensors in the ServiceNow instance then process this data and update the CMDB accordingly.

    Multiprobes are probes that include multiple individual probes, and multisensors correspondingly process their combined data with scripts for each included probe.

    Probe Types and Usage

    • Windows computers and servers: Use remote WMI queries and shell commands.
    • UNIX/Linux servers: Use shell commands via SSH (Bourne-compatible shells supported).
    • Storage devices: Use CIM/WBEM queries.
    • Printers and network gear (switches, routers): Use SNMP queries.
    • Web servers: Use HTTP header examination.
    • Uninterruptible Power Supplies (UPS): Use SNMP queries.

    Managing Probes and Sensors

    Most probes and sensors are included out-of-the-box and rarely require modification. However, customers who have customized probes must align their probe and sensor versions after upgrades to ensure compatibility.

    Multiprobes and multisensors facilitate multiple queries with a single authentication to efficiently gather device data.

    Customization Example

    An example of a custom probe is one that reads a text file on a Windows computer and populates a CI in the CMDB with its values. This demonstrates how probes can be tailored to specific data collection needs.

    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