--- 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 --- # Create or modify a probe # Create or modify a probe {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Create a new probe to discover additional CIs or modify an existing probe to collect additional information. After you create or modify a probe, test it. ## Before you begin Role required: admin Important: You need an advanced knowledge of scripting to modify probes or their associated sensors. Many existing probes provide parameters that you can set, rather than modifying the probe itself. See [Set probe parameters](https://servicenow-prod.fluidtopics.net/UHZBnXmoydOuoy0I74kSWA "Use probe parameters to control the behavior of a particular probe every time it is triggered.") for more information. ## Procedure 1. Navigate to AllDiscoveryDiscovery DefinitionProbes. 2. Click the name of the probe that you want to modify. 3. Modify the form fields (see table). {#modify-a-probe__table_k53_2dv_tp__entry__2} | Field | Description | |-|-| | Class | Select the probe for the operating system of the device it will query. * AWS Probe: Select this class to query your resources inside an AWS cloud. * [CIM Probe](https://servicenow-prod.fluidtopics.net/GXvTH_Iwclc3iqPIkbNwXA#r_CIMProbe "The CIM probe uses WBEM protocols to query a particular CIM server, the CIM Object Manager, for a set of data objects and properties."): Select this probe type to query a CIM server using WBEM protocols. * [Multiprobe](https://servicenow-prod.fluidtopics.net/d~uAmStwz2Y3bx50t2CPpA#t_MultiprobesAndMultisensors "You can use the default multiprobes and multisensors provided in the platform or create your own."): Select this probe type to run one or more simple probes of any type or mix probes of different types. This type of probe can make several queries simultaneously that return all the results at the same time. You cannot add multiprobes to other multiprobes. * Probe: Select this generic type to define a probe class. Specify the name of the probe class in the ECC queue topic field. * [SNMP Probe](https://servicenow-prod.fluidtopics.net/JflbrwQ6DImKDYeGq7Qf4g "The SNMP probes use the SNMP protocol to query a particular device for a list of OIDs, which are then traversed and the results passed back to the sensors. MID Servers support all SNMP protocol versions by default. You can set a MID Server to only support specific versions of SNMP."): Select this probe type for network devices, such as routers. * [WMI Probe](https://servicenow-prod.fluidtopics.net/tbZva~OshchU7fq2q52o4w "WMI Runner is a probe type that fetches data from Windows operating systems via the Windows Management Instrumentation (WMI) interface. IPv6 supports WMI Runner."): Select this probe type for Windows devices. {#modify-a-probe__ul_wrp_3dv_tp} | | ECC queue topic | Enter a descriptive term for the function of the probe. The probe uses this label as the Topic field for incoming ECC queue messages. The term does not have to be unique. For example, all the UNIX probes might have an ECC queue topic value of SSHCommand. By default, probes use the following ECC queue topics: * CimProbe * Multiprobe * Powershell probe * SCPRelay * SSHCommand * SNMP * WMIRunner {#modify-a-probe__ul_m2s_n2v_tp} | | ECC queue name | Enter either a descriptive name for human use, or the actual command the probe is to run. For example, if the value in the ECC queue topic field is SSHCommand, then enter the actual shell command to run in this field. | | Cache results | Select this option to cache this probe's results to improve overall discovery performance. The probe results cache should be enabled only for those probes and sensors whose output is unlikely to change. For example, the Linux -- CPU sensor is cached because CPU information seldom changes. The cache is turned on by default for base system probes and sensors whose output is unlikely to change. Warning: Do not turn on the cache for classification and identification probes. Furthermore, do not turn on the cache for probes that trigger additional probes because this may prevent them from being triggered. | | Classic Mode | Select this option to cache this probe's results in the Starting in Fuji, select this option to debug the post-processing script on the ServiceNow instance instead of the MID Server. This mode is only valid if a post-processor script exists. Use the Classic mode to debug post-processing scripts in the test environment. ServiceNow does not recommend use of the Classic mode in the production environment. | | Post processor script | Define an optional post-processing script that runs on the MID Server. The script accepts probe results as an input and outputs a JSON string that is sent back to the instance for a sensor to use as input. Use this type of script to accomplish tasks like parsing data. All probe post-processing scripts and their corresponding sensors have access to the following global variables: * `current`: Sets the attribute to current. Same functionality that exists in sensors. They are attributes of the device that is discovered. * `related_data`: Any additional data to be passed from the probes post-processing scripts, such as `related_list`. {#modify-a-probe__ul_y3c_wdp_2fb} All probe post-processing scripts and their corresponding sensors have access to the following methods: * `log(string)`: Logs the string to the MID Server and the ServiceNow instance log files. * `getParameter(param)`: Gets the parameter from the ECC queue payload. {#modify-a-probe__ul_qcf_xdp_2fb} | [ ] {#modify-a-probe__table_k53_2dv_tp} 4. Right-click the form header and select Save. 5. Modify these related lists if necessary. {#modify-a-probe__table_chn_p2f_dcb__entry__2} | Related list | Description | |-|-| | Probe Parameters | Parameters that control the functionality of the probe. See [Set probe parameters](https://servicenow-prod.fluidtopics.net/UHZBnXmoydOuoy0I74kSWA "Use probe parameters to control the behavior of a particular probe every time it is triggered.") for instructions. | | Sensors that react to this probe or Sensors | The sensors that this probe utilizes. | | Included by MultiProbe | If this probe is included with other probes as a MultiProbe. | | MultiSensor Scripts | Scripts that run for multiple sensors. | | Versions | The version of the probe. If the State is Current, the probe is the most up to date with your version of the instance. If not, you do not have the most current version and you might need to realign it. See [Align versions of customized probes and sensors](https://servicenow-prod.fluidtopics.net/RoFIyn73nJB8CElKjpLU0Q "If you customized a probe or sensor and upgraded to a new version of an instance, you need to realign the versions of the customized probe and sensor to the most current version.") for instructions. | [ ] {#modify-a-probe__table_chn_p2f_dcb} 6. Click Test probe. 7. On the Test Probe window, enter the IP address of the target and select the MID Server. Only Up and Validated MID Servers are able to be selected. 8. Click OK. 9. [Check the ECC Queue](https://servicenow-prod.fluidtopics.net/bpcRyGIfqThsVq23q3BEJg "The External Communication Channel (ECC) Queue is a connection point between your ServiceNow instance and other systems that integrate with it, most commonly a MID Server.") for the MID Server to see the results. ## What to do next Add the probe to the Triggers Probe related list on the appropriate classifier. See [Create a Discovery CI classification](https://servicenow-prod.fluidtopics.net/IIbCQw4jyfDYfm6OcHRBIA "A CI classification allows Discovery to discover most common operating systems, network devices, and processes.") for a description of the fields and related lists on the classifier form. *[\>]: and then