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

Configure and run the vCenter event collector extension

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

Configure and run the vCenter event collector extension

Configure the vCenter event collector extension in the MID Server module, and then add or remove supported events.

Before you begin

Before configuring event collectors, perform these tasks:
  • Deploy and start a MID Server.
  • Ensure that the MID Server has access to the vCenter.
  • Run discovery on the vCenter.

Role required: agent_admin, admin

About this task

Multiple MID Servers can listen to the same vCenter instance, but each MID Server and each vCenter can have only one event collector record associated with it. Make sure you configure the events on the event collector record that specifies the correct MID Server.
Note: You can add events to the vCenter event collector. However, not every event is supported by the base system event handlers. If you want to handle events other than those supported in the base Discovery system, you must create a script action to process the events. For instructions, see Script actions. As a reference, the instance processes the vCenter events in the base system with a script action called Discovery: Process vCenter events. Do not edit or delete this script action.

To configure the vCenter event processor extension:


  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.
  4. Right-click in the header bar and click Save in the context menu.
    The vCenter Event related list appears, containing the default events that the system is configured to handle.
  5. To select a different vCenter event, click Edit in the vCenter Event related list and browse for the event.

    The slushbucket does not display all the available events in the opening list. Use the filter to browse for events not displayed.

  6. Under Related Links click Start to save the events in this collection and start the collector.
    The Related Links in this form work as follows:
    Table 1. Commands available in the vCenter event processor extension
    Related Link Description
    Start Starts the collector if it is not running. The extension connects to the specified vCenter server by enumerating the VMware credentials in the credential set until a connection can be made. Next, the extension tells the vCenter server to supply the events specified in the Collector Context.
    Stop Stops the running collector on the configured MID Server. No action is taken if the extension is not running.
    Restart Stops, then starts the collector on the configured MID Server.
    Test Tests the parameters for validity. If the IP address, hostname, and the set of events is valid then the test returns a successful status. If any of the parameters are incorrect, an error is shown. Running a test does not affect any extensions that are currently running.
    Update parameters Sends updated parameters to the collector. Any changes you make to the collector while the MID Server is running do not take effect immediately when they are saved. If you click this control when the collector is not running, no update is made.

    In the case of the vCenter extension, the collector first tests the parameters for validity. If the parameters are valid, the extension disconnects from the vCenter server and reconnects with the new parameters.

    Event collector
    Field Description
    Name A unique name for this vCenter event collector extension for easy identification.
    Short description A description of this collector.
    Extension [Read-Only] The collector type is automatically set to vCenterExtension.
    Status This field auto-populates with the status of the collector. This field is blank until the collector is started. After issuing a command to the collector, you see one of these values:
    • Started: The collector is running.
    • Stopped: The collector is not running.
    • Offline: The MID Server is down.
    • Error: The collector failed with an error.
    Note: The MID Server continues to process vCenter events, even if it is paused. The status of the event collector may show as Started.
    Error Message Message describing any error that causes a command, such as Start or Stop, to fail. This field only appears when the value in the Status field is Error.
    Execute on Location for running this collection. The possible options are Specific MID Server or 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. If you selected the MID Server cluster option, an algorithm determines which server in the cluster runs the collector.
    vCenter The IP address or hostname of the vCenter server.
    Executing on [Read-Only] The name of the MID Server on which the collector is running. This field shows the name of the MID Server even if the MID Server is down. If the collector is stopped by the user, this field is empty.