Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Operations Management
Table of Contents
Choose your release version
    Home London IT Operations Management IT Operations Management Discovery Advanced Discovery configuration vCenter event collector Configure and run the vCenter event collector extension

    Configure and run the vCenter event collector extension

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    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:

    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.
    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.
      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.
    Related concepts
    • VMware discovery

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Configure and run the vCenter event collector extension

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      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:

      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.
      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.
        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.
      Related concepts
      • VMware discovery

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login