Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Trigger custom probes with the vCenter Discovery extension

Log in to subscribe to topics and get notified when content changes.

Trigger custom probes with the vCenter Discovery extension

vCenter Discovery extension allows you to collect additional attributes of currently discovered CI types or collect attributes of new CI types by triggering custom probes from an existing sensor.

About this task

vCenter sensor records support triggering custom probes that use conditional scripts for gathering data not typically collected by Discovery or for discovering CI types that you create.

Role required: admin

Caution: The vCenter extension is intended to be used to create a single custom probe that extends existing Discovery functionality. Unless you are a user who is familiar with advanced scripting, do not attempt to configure your new probe/sensor to launch an additional probe.


  1. Navigate to Discovery Definition > Sensors.
  2. Select a vCenter sensor record.
    It is important to trigger a new probe at the correct time. For example, if you want to discover additional information about virtual machines in your network, trigger your probe from the VMWare - vCenter VMs sensor. If you trigger your custom probe from the VMWare - vCenter Datacenters sensor, your new probe and the existing VM probe execute in parallel. This might prevent VM records from being created or updated.
  3. Select the Triggers probes related list.
  4. Click New to create a new probe to be triggered by this sensor or Edit to add an existing probe to the list.
    You can also use an existing probe record as a template for your new probe by opening the record and selecting the Insert and Stay option from the context menu.
  5. Click the information icon to the right of the probe name to open the Conditional Probes Triggered by Sensor record.
  6. View the script.
    The script passes the parms and data arguments to the function, using values passed to them from the triggering sensor. The script configures the parms object, from which the probe parameters are derived. The script returns true to trigger the probe or false to cancel it.

    In this example, the VMWare – vCenter Datacenters sensor parms are all probe parameters that are supported by the Datacenters probe. The data argument is an object containing up to 4 arrays, named vm, datastore, network, and cluster.

    Figure 1. Conditional Probes Triggered by Sensor record
    Conditional Probes Triggered by Sensor record