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 Event Management Administer events Event collection configuration Configure event collection that uses pull operation Configure event collection from Hyperic

    Configure event collection from Hyperic

    • 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 event collection from Hyperic

    Configure the Hyperic connector instance to receive events from the VMware vRealize Hyperic server.

    Before you begin

    Role required: evt_mgmt_admin

    Supported version: 5.8.4.0

    Procedure

    1. Navigate to Event Management > Event Connectors (Pull) > Connector Instances.
    2. Click New and create a Hyperic connector instance with the following details:
      Field Value
      Name Specify a unique name for the Hyperic connector instance.
      Host IP Specify the Hyperic IP address.
      Credential In the Credentials form, click New and create the required credentials. Save the credentials using a unique and recognizable name, for example, HypericOPS.
      Schedule (seconds) The frequency in seconds that the system checks for new events from Hyperic.
      Description Type a description for the use of the Hyperic event collection instance.
      Connector definition The vendor and protocol used to gather events from the external event source. Select the Hyperic connector definition.
      Last error message The last error message is automatically updated.
      Last run time The last run time value is automatically updated.
      Last run status The last run time status is automatically updated.
      MID Servers (MID Server for Connectors section) Optional. Name of a MID Server. If no MID Server is specified, an available MID Server that has a matching IP range is used. In the MID Servers for Connectors section, specify a MID Server that is up and valid. You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on. MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section.
    3. Right-click the form header and select Save.
      The connector instance values are added to the form and the parameters that are relevant to the connector appear.
    4. In the Connector Parameters section, specify the values of the mandatory Hyperic parameters.
      1. port Default value 7080.
      2. protocol Default value http.
    5. Click Test connector to verify the connection between the MID Server and the Hyperic connector.
    6. If the test fails, follow the instructions that are issued by the error to correct the problem and then run another test.
      Note: Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to the Hyperic server.
    7. After a successful test, select the Active check box and then click Update.
    Related tasks
    • Configure a connector instance

    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 event collection from Hyperic

      • 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 event collection from Hyperic

      Configure the Hyperic connector instance to receive events from the VMware vRealize Hyperic server.

      Before you begin

      Role required: evt_mgmt_admin

      Supported version: 5.8.4.0

      Procedure

      1. Navigate to Event Management > Event Connectors (Pull) > Connector Instances.
      2. Click New and create a Hyperic connector instance with the following details:
        Field Value
        Name Specify a unique name for the Hyperic connector instance.
        Host IP Specify the Hyperic IP address.
        Credential In the Credentials form, click New and create the required credentials. Save the credentials using a unique and recognizable name, for example, HypericOPS.
        Schedule (seconds) The frequency in seconds that the system checks for new events from Hyperic.
        Description Type a description for the use of the Hyperic event collection instance.
        Connector definition The vendor and protocol used to gather events from the external event source. Select the Hyperic connector definition.
        Last error message The last error message is automatically updated.
        Last run time The last run time value is automatically updated.
        Last run status The last run time status is automatically updated.
        MID Servers (MID Server for Connectors section) Optional. Name of a MID Server. If no MID Server is specified, an available MID Server that has a matching IP range is used. In the MID Servers for Connectors section, specify a MID Server that is up and valid. You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on. MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section.
      3. Right-click the form header and select Save.
        The connector instance values are added to the form and the parameters that are relevant to the connector appear.
      4. In the Connector Parameters section, specify the values of the mandatory Hyperic parameters.
        1. port Default value 7080.
        2. protocol Default value http.
      5. Click Test connector to verify the connection between the MID Server and the Hyperic connector.
      6. If the test fails, follow the instructions that are issued by the error to correct the problem and then run another test.
        Note: Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to the Hyperic server.
      7. After a successful test, select the Active check box and then click Update.
      Related tasks
      • Configure a connector instance

      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