---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Creating an event rule to map metrics to specific CIs

# Creating an event rule to map metrics to specific CIs {#ariaid-title1}

* Release version: Yokohama
* 
* Updated June 29, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create event rules to map incoming raw metric data to specific CIs, to optionally modify
metric names, and to populate the resource_path attribute for resource
binding.
The system generates events for every new raw metric data for which there are no CI binding
specifications. You can create event rules that filter those events to map the incoming metric
data to specific CIs. In such event rules, you can for example define a filter that is based on
the monitoring object (such as SCOM).

To use resource binding, the resource_path attribute of events must be
populated. You can configure an event rule to ensure that the resource_path
attribute is included in the Additional information field in events. For
more information about configuring and using resource binding, see [resource binding](https://servicenow-prod.fluidtopics.net/by_1zowEeXdGDWzuLMiTAQ "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.").

Use the resource_path attribute to identify the resource within the bound CI. For example, if a metric is collected for the C drive of the `win_server_001` CI, set
resource_path to a value such as `Disk - C`. The metric identifier can then use the `CI/Resource/Metric` format, such as `win_server_001/Disk -
C/disk_usage`.

For example, in the Event Rule designer you can update the
event rule SCOM IIS Web Server as follows:{#event-rule-bind-metrics-to-ci__p_ExampleMetricsEventRule}

* On the Event Filter tab, define filter to match only IIS Web Servers.
* On the Binding tab, set Class to <kbd class="ph userinput">Microsoft IIS Web Server</kbd>.
{#event-rule-bind-metrics-to-ci__ul_vcl_npy_wy}
**Related concepts**   

* [Event rules](https://servicenow-prod.fluidtopics.net/NAsCQ7ocCYVbIwhpy8vV2w "Use event rules to generate alerts for tracking and remediation. Event rules are stored in the Event Rule [em_match_rule] table. Configure and customize event rules to manage events and alert generation.")  
**Related tasks**   

* [View metric to CI and resource binding](https://servicenow-prod.fluidtopics.net/VzN0cOeVu9DqXsAlN7cZfg "View the metric to CI and resource binding results, including details for failed bindings which you can use to mitigate the failure. If Metric Intelligence cannot map and bind a metric to a CI or to a resource, then that CI or resource is not included in anomaly detection until it is properly mapped.")
* [Get started with Metric Intelligence](https://servicenow-prod.fluidtopics.net/uhvvnrDS_P1UFMf28Tmdnw "Complete the following setup and initial configuration steps to start using Metric Intelligence.")