Configure the vCenter event processor extension

Configure this extension in the MID Server module.

Before you begin

Role required: Admin

About this task

To configure the vCenter event processor extension:

Procedure

  1. Navigate to MID Server > Extensions > vCenter Event Collectors.
  2. Click New or open an existing extension.
  3. Fill in the fields, as appropriate from the table.
    Reference the vCenter Event Processor Extension Form table, as needed.
  4. Click Submit or Update.
    vCenter event collector form
    Table 1. vCenter event collector form
    Field name Description
    Name A unique name for this vCenter event collector extension for easy identification.
    Short description A description of the MID Server extension, if more description than the Name is necessary.
    Extension [Read-Only] The extension type is automatically set to vCenterExtension.
    Status This field auto-populates with the status of the extension. This field is blank until the extension is run. After it is run, the value may be:
    • Started: The extension is running.
    • Stopped: The extension is not running.
    • Offline: The MID Server is down.
    • Error: The extension failed with an error.
    Execute on The location for running this extension: a Specific MID Server or a Specific MID Server Cluster.
    MID Server The name of the designated MID Server if you selected Specific MID Server in the Execute on field. The name of the designated MID Server cluster if you selected Specific MID Server Cluster in the Execute on field. If you selected Specific MID Server Cluster, a ServiceNow algorithm determines which server in the cluster runs the extension.
    vCenter The IP address or hostname of the vCenter server.
    events A comma-separated list of events that are reported to the instance for processing. Use any combination of the following valid options:
    • VmPoweredOnEvent: The virtual machine (VM) has been powered on from the powered off state or resumed from the suspended state. This event is sent as soon as the VM is powered on, it does not take into account the time it may take to boot the host OS.
    • VmPoweredOffEvent: The virtual machine has been powered off. If the host OS is shut down, this event is sent after the host OS shuts down and the VM enters the powered off state.
    • VmSuspendedEvent: The virtual machine has been suspended. This event is sent after the VM suspension is complete.
    • VmRelocatedEvent: The virtual machine has been relocated while offline (either suspended or powered off). This event is triggered by either a VM migration of the VM to a different host, or the migration of any storage used by the VM.
    • VmMigratedEvent: One or both of the following occurs:
      • The virtual machine has been hot migrated, with vMotion, to another ESX server
      • The storage for the VM has been hot migrated.
    Executing on [Read-Only] The name of the MID Server on which the extension is running. This field shows the name of the MID Server even if the MID Server is down. If the extension is stopped by the user, this field is empty.