Creating an event rule to map metrics to specific CIs
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- IT Operations Management
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.
For example, in the Event Rule designer you can update the event rule SCOM IIS Web Server as follows:
- On the Event Filter tab, define filter to match only IIS Web Servers.
- On the Binding tab, set Class to Microsoft IIS Web Server.
Related Content
- Event rules
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.
- View metric to CI and resource binding
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
Complete the following setup and initial configuration steps to start using Metric Intelligence.