{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29696,"path":"it-operations-management/discovery/modify-a-probe.md","title":"Create or modify a probe","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create or modify a probe\n\nCreate 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.\n\n## Before you begin\n\nRole required: admin\n\n**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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_SetProbeParameters.md) for more information.\n\n## Procedure\n\n1. Navigate to **All** > **Discovery** > **Discovery Definition** > **Probes**.\n\n2. Click the name of the probe that you want to modify.\n\n3. Modify the form fields \\(see table\\).\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nClass\n\n\n\nSelect 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.\n- [**CIM Probe**](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_CIMProbe.md): Select this probe type to query a CIM server using WBEM protocols.\n- [**Multiprobe**](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_MultiprobesIncludedWithDiscovery.md): 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.\n- **Probe**: Select this generic type to define a probe class. Specify the name of the probe class in the ECC queue topic field.\n- [**SNMP Probe**](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/c_SNMPProbe.md): Select this probe type for network devices, such as routers.\n- [**WMI Probe**](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_WMIRunnerProbe.md): Select this probe type for Windows devices.\n\n\n
\n\nECC queue topic\n\n\n\nEnter 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:\n\n- CimProbe\n- Multiprobe\n- Powershell probe\n- SCPRelay\n- SSHCommand\n- SNMP\n- WMIRunner\n\n\n
\n\nECC queue name\n\n\n\nEnter 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.\n\n
\n\nCache results\n\n\n\nSelect 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.\n\n
\n\nClassic Mode\n\n\n\nSelect 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.\n\n
\n\nPost processor script\n\n\n\nDefine 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:\n\n- `current`: Sets the attribute to current. Same functionality that exists in sensors. They are attributes of the device that is discovered.\n- `related_data`: Any additional data to be passed from the probes post-processing scripts, such as `related_list`.\n All probe post-processing scripts and their corresponding sensors have access to the following methods:\n\n- `log(string)`: Logs the string to the MID Server and the ServiceNow instance log files.\n- `getParameter(param)`: Gets the parameter from the ECC queue payload.\n\n\n
4. Right-click the form header and select **Save**.\n\n5. Modify these related lists if necessary.\n\n |Related list|Description|\n |------------|-----------|\n |Probe Parameters|Parameters that control the functionality of the probe. See [Set probe parameters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_SetProbeParameters.md) for instructions.|\n |Sensors that react to this probe or Sensors|The sensors that this probe utilizes.|\n |Included by MultiProbe|If this probe is included with other probes as a MultiProbe.|\n |MultiSensor Scripts|Scripts that run for multiple sensors.|\n |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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_AlignVerCustProbeSens.md) for instructions.|\n\n6. Click **Test probe**.\n\n7. On the Test Probe window, enter the IP address of the target and select the MID Server.\n\n Only **Up** and **Validated** MID Servers are able to be selected.\n\n8. Click **OK**.\n\n9. [Check the ECC Queue](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_DiscoveryStatusECCQueue.md) for the MID Server to see the results.\n\n\n## What to do next\n\nAdd the probe to the **Triggers Probe** related list on the appropriate classifier. See [Create a Discovery CI classification](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/create-discovery-ci-classification.md) for a description of the fields and related lists on the classifier form.\n\n**Parent Topic:**[Discovery probe management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_Probes.md)\n\n"}}