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 Orlando IT Operations Management IT Operations Management ITOM Health Event Management Administer events Event rules Alert binding to CIs with event rules Bind alerts for non-host CIs

    Bind alerts for non-host CIs

    • 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

    Bind alerts for non-host CIs

    An incoming event from a discovered application service or alert group can bind to an alert based on an event rule and the corresponding event field mapping. The event field mapping requires a URL or the port number and corresponding IP address for each service or alert group.

    Before you begin

    Role required: evt_mgmt_admin

    About this task

    If the event is specific to a non-host CI, for example an application service or alert group, use these steps to bind alerts to a non-host CI:
    • Leave the Node field empty.
    • Populate the CI Type with the CI type you want to bind.
    • Make sure the additional_info field has enough information to uniquely identify the CI. The algorithm matches all additional_info attributes that have the same name as CI fields for that Event Type. If the match is successful, the event will be bound to the CI.
    Optional method:
    • Leave the Node field empty.
    • Populate the CI Identifier (ci_identifier) field with attributes, as described above, that uniquely identify the CI.

    Procedure

    1. Navigate to Event Management > Rules > Event Rules.
    2. Click New and fill in the appropriate fields of the event rule.
    3. Click Transform.
    4. From the CI type list, select cmdb_ci_service_auto.
    5. In the Event Match Fields section, insert a new row with these parameter values:
      Field Value
      Field node
      Regular Expression (.*)
      Mapping temp node
    6. In the Event Compose Fields section, insert a new row with these parameter value:
      Field Value
      Field node
      Composition (empty)
    7. Click Submit.
    8. Navigate to Event Management > Rules > Event Field Mapping.
    9. Create the corresponding event field mapping with these parameter values:
      Field Value
      Source Specify the event monitor software that generated the event.
      Mapping type Select Single field.
      From field Specify temp node.
      To field Specify name.
    10. In the Event Mapping Pairs section, insert new rows for each event mapping pair.
      1. Set the Key with the URL or an IP address with corresponding port value.
      2. Set the Value with the discovered application service, technical service, or alert group name.
      For example, you can add an event mapping pair for each service.
      event mapping pair

    11. Click Submit.
    Related tasks
    • Create event field mappings
    Related reference
    • Alert binding to CIs with event rules

    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

      Bind alerts for non-host CIs

      • 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

      Bind alerts for non-host CIs

      An incoming event from a discovered application service or alert group can bind to an alert based on an event rule and the corresponding event field mapping. The event field mapping requires a URL or the port number and corresponding IP address for each service or alert group.

      Before you begin

      Role required: evt_mgmt_admin

      About this task

      If the event is specific to a non-host CI, for example an application service or alert group, use these steps to bind alerts to a non-host CI:
      • Leave the Node field empty.
      • Populate the CI Type with the CI type you want to bind.
      • Make sure the additional_info field has enough information to uniquely identify the CI. The algorithm matches all additional_info attributes that have the same name as CI fields for that Event Type. If the match is successful, the event will be bound to the CI.
      Optional method:
      • Leave the Node field empty.
      • Populate the CI Identifier (ci_identifier) field with attributes, as described above, that uniquely identify the CI.

      Procedure

      1. Navigate to Event Management > Rules > Event Rules.
      2. Click New and fill in the appropriate fields of the event rule.
      3. Click Transform.
      4. From the CI type list, select cmdb_ci_service_auto.
      5. In the Event Match Fields section, insert a new row with these parameter values:
        Field Value
        Field node
        Regular Expression (.*)
        Mapping temp node
      6. In the Event Compose Fields section, insert a new row with these parameter value:
        Field Value
        Field node
        Composition (empty)
      7. Click Submit.
      8. Navigate to Event Management > Rules > Event Field Mapping.
      9. Create the corresponding event field mapping with these parameter values:
        Field Value
        Source Specify the event monitor software that generated the event.
        Mapping type Select Single field.
        From field Specify temp node.
        To field Specify name.
      10. In the Event Mapping Pairs section, insert new rows for each event mapping pair.
        1. Set the Key with the URL or an IP address with corresponding port value.
        2. Set the Value with the discovered application service, technical service, or alert group name.
        For example, you can add an event mapping pair for each service.
        event mapping pair

      11. Click Submit.
      Related tasks
      • Create event field mappings
      Related reference
      • Alert binding to CIs with event rules

      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