---
sourceDocument: Xanadu IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-operations-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Metric Configuration Rules

# Metric Configuration Rules {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Metric configuration rules enable you to determine how incoming metrics from the Agent Client Collector are to be processed.

When a new metric arrives from an Agent Client Collector, a new record is
created in the Metric to CI Mappings table, with the value, Anomaly Detection Action Level = Bounds.

To trigger execution of a metric configuration rule, navigate to the Metric Configuration Rules
table (Event ManagementAnomaly DetectionMetric Config Rules) and select the Sync to MID button at the top of the
page. This also synchronizes all MID Servers connected to the instance.

When executing the rule, the anomaly detection action level defined in the rule (set by the
anomaly_detection_action_level parameter) retroactively overrides the
anomaly detection action level configured for the metric in the Metric to CI Mappings
table.

If you do not trigger the rule execution, retroactive overriding of the Anomaly detection action level parameter is performed during execution of the hourly
scheduled Metric Intelligence - Metric configuration job.

When configuring a metric configuration rule, rules with a filter run before rules with no
filter. When multiple rules have the same priority, the most recently configured rule runs
first.

For details on creating configuration settings rules, see [Create a configuration settings rule](https://www.servicenow.com/docs/0EqZoYBVif5njzGfXI2qPA "Configuration settings affect how metric data is processed. Configuration settings rules override the default metric processing behavior to determine the system actions when an anomaly is detected.").

For details on the available anomaly detection action levels, see [Configure the action level of anomaly detection](https://www.servicenow.com/docs/JHXf018iFLxa_1a6hN~1zA "Create a configuration setting rule that refines the level of anomaly detection processing and analysis that is applied to specific CIs and metrics. Set a processing level that reflects the importance of metrics at different stages of implementation, to reduce data load if needed.").

*[\>]: and then