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 New York IT Operations Management IT Operations Management ITOM Health Operational Intelligence Metric binding Metric binding to resources

    Metric binding to resources

    • 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

    Metric binding to resources

    Bind metrics to resources to simplify metric events binding by enabling binding to resources such as specific disks or web pages, in addition to binding to CIs.

    Operational Intelligence models metric series in either of the following methods:
    • Binding a metric series to a CI and to the metric being monitored for that CI using a 'CI/Metric' format. For example, 'win_server_001/response_time_mean'.
    • Binding a metric series to a CI, a resource within that CI, and the metric being monitored for that resource, using a 'CI/Resource/Metric' format. For example, 'win_server_001/Disk — C/disk_usage'. This method is referred to as 'resource binding'.
    The first method enables modeling, storing, aggregating, and querying data at the CI level. However, resource binding creates resource records for specific monitored entities, such as an individual web page or a disk. Therefore, resource binding is more efficient when there are multiple resources of similar types within a CI, and metrics applicable to a category of these resources are mapped to these resources.
    Use cases:
    • Common examples are disks, processors, and network interfaces. In cases in which these entities are being monitored but do not exist in the CMDB, using resources for metric binding is useful.
    • Some monitoring solutions capture metric data within services such as KPIs for individual web pages in an application. In such cases where the entity being monitored is not a configuration item, metric binding to resources can be helpful.
    In those situations, using resource binding results in more meaningful aggregations across similar metrics (such as: avg disk_usage for a host across all disks).

    Resource binding process

    The MID Server generates metric binding events that are processed by the instance. When processing a metric binding event, there is an attempt to identify the CI to which this metric binding event belongs. If this attempt is successful, then the metric binding event is bound to the identified CI and binding to a resource is attempted. The following steps describe the attempt to bind a metric binding event to a resource:
    1. Identify the CI class of the CI that was bound to the metric binding event.
    2. Locate the resource class which is mapped to that CI class (using the CI Type To Resource Class [sa_ci_type_to_resource_class] table).
    3. Read the resource_path attribute value in the additional_information field in the metric binding event.
    4. Check if a resource record exists in the resource class table, in which name is equal to resource_path and cmdb_ci is equal to the CI that was bound to the metric binding event.
    5. If such resource record exists, then the metric binding event is bound to that resource. Otherwise, a new resource record is created with the preceding values and the metric binding event is bound to the newly created resource.

    Configure resource binding

    • Ensure that the sa.metric.use.resource.binding system property is set to true (default).
    • For series intended to be bound to resources, ensure that the resource_path attribute is populated by doing either step:
      • Use an event rule to add the resource_path attribute to the Additional information field in events. For more information, see Create an event rule to map metrics to specific CI.
      • Populate the resource_path attribute as a part of the respective CI identifier when data is sent to the MID Server for processing.
    • Review the default mappings in the CI Type To Resource Class [sa_ci_type_to_resource_class] table and adjust as needed. It is critical that mappings are set as desired prior to data processing.

      Managing the CI Type To Resource Class table requires the evt_mgmt_admin role.

    Resource tables

    Resource binding uses an underlying hierarchy structure of resources which is a subset of the [cmdb_ci] hierarchy. Operational Intelligence installs the following resource tables:
    • CI Resource [ci_resource] (parent table):
    • Tables that extend CI Resource [ci_resource]:
      • ci_resource_hardware
      • ci_resource_appl
      • ci_resource_service
      • ci_resource_vm_object
      • ci_resource_database

    Mapping CIs to resources

    Mappings of CI classes to resource classes are stored in the CI Type To Resource Class [sa_ci_type_to_resource_class] table. This table is installed with Operational Intelligence, and is used during metric binding to resources.

    Table 1. Mappings in the CI Type To Resource Class table (default)
    CI class Resource class
    cmdb_ci_hardware ci_resource_hardware
    cmdb_ci_appl ci_resource_appl
    cmdb_ci_service ci_resource_service
    cmdb_ci_database ci_resource_database
    cmdb_ci_vm_object ci_resource_vm_object

    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

      Metric binding to resources

      • 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

      Metric binding to resources

      Bind metrics to resources to simplify metric events binding by enabling binding to resources such as specific disks or web pages, in addition to binding to CIs.

      Operational Intelligence models metric series in either of the following methods:
      • Binding a metric series to a CI and to the metric being monitored for that CI using a 'CI/Metric' format. For example, 'win_server_001/response_time_mean'.
      • Binding a metric series to a CI, a resource within that CI, and the metric being monitored for that resource, using a 'CI/Resource/Metric' format. For example, 'win_server_001/Disk — C/disk_usage'. This method is referred to as 'resource binding'.
      The first method enables modeling, storing, aggregating, and querying data at the CI level. However, resource binding creates resource records for specific monitored entities, such as an individual web page or a disk. Therefore, resource binding is more efficient when there are multiple resources of similar types within a CI, and metrics applicable to a category of these resources are mapped to these resources.
      Use cases:
      • Common examples are disks, processors, and network interfaces. In cases in which these entities are being monitored but do not exist in the CMDB, using resources for metric binding is useful.
      • Some monitoring solutions capture metric data within services such as KPIs for individual web pages in an application. In such cases where the entity being monitored is not a configuration item, metric binding to resources can be helpful.
      In those situations, using resource binding results in more meaningful aggregations across similar metrics (such as: avg disk_usage for a host across all disks).

      Resource binding process

      The MID Server generates metric binding events that are processed by the instance. When processing a metric binding event, there is an attempt to identify the CI to which this metric binding event belongs. If this attempt is successful, then the metric binding event is bound to the identified CI and binding to a resource is attempted. The following steps describe the attempt to bind a metric binding event to a resource:
      1. Identify the CI class of the CI that was bound to the metric binding event.
      2. Locate the resource class which is mapped to that CI class (using the CI Type To Resource Class [sa_ci_type_to_resource_class] table).
      3. Read the resource_path attribute value in the additional_information field in the metric binding event.
      4. Check if a resource record exists in the resource class table, in which name is equal to resource_path and cmdb_ci is equal to the CI that was bound to the metric binding event.
      5. If such resource record exists, then the metric binding event is bound to that resource. Otherwise, a new resource record is created with the preceding values and the metric binding event is bound to the newly created resource.

      Configure resource binding

      • Ensure that the sa.metric.use.resource.binding system property is set to true (default).
      • For series intended to be bound to resources, ensure that the resource_path attribute is populated by doing either step:
        • Use an event rule to add the resource_path attribute to the Additional information field in events. For more information, see Create an event rule to map metrics to specific CI.
        • Populate the resource_path attribute as a part of the respective CI identifier when data is sent to the MID Server for processing.
      • Review the default mappings in the CI Type To Resource Class [sa_ci_type_to_resource_class] table and adjust as needed. It is critical that mappings are set as desired prior to data processing.

        Managing the CI Type To Resource Class table requires the evt_mgmt_admin role.

      Resource tables

      Resource binding uses an underlying hierarchy structure of resources which is a subset of the [cmdb_ci] hierarchy. Operational Intelligence installs the following resource tables:
      • CI Resource [ci_resource] (parent table):
      • Tables that extend CI Resource [ci_resource]:
        • ci_resource_hardware
        • ci_resource_appl
        • ci_resource_service
        • ci_resource_vm_object
        • ci_resource_database

      Mapping CIs to resources

      Mappings of CI classes to resource classes are stored in the CI Type To Resource Class [sa_ci_type_to_resource_class] table. This table is installed with Operational Intelligence, and is used during metric binding to resources.

      Table 1. Mappings in the CI Type To Resource Class table (default)
      CI class Resource class
      cmdb_ci_hardware ci_resource_hardware
      cmdb_ci_appl ci_resource_appl
      cmdb_ci_service ci_resource_service
      cmdb_ci_database ci_resource_database
      cmdb_ci_vm_object ci_resource_vm_object

      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