---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Configure the action level for anomaly detection

# Configure the action level for anomaly detection {#ariaid-title1}

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

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.
Anomaly detection consists of multiple levels of processing. At the lowest level, metric data
is gathered from data sources. At the highest level, statistical models are created, anomaly
scores are calculated, and anomaly alerts and IT alerts are created. You can apply the full
anomaly detection process or a reduced level of processing, for specific data series.

Use the anomaly_detection_action_level configuration setting in a [configuration setting rule](https://www.servicenow.com/docs/6kxDdt9Pd2xc3hNJKumvUg "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.") to set the level of processing for specific
CIs and metrics. For example, you can initially set only a small percentage of CIs and metrics
to generate anomaly alerts, and later increase that percentage.

## Action levels {#configure-level-anomaly-detection__section_yt1_4cw_2hb}

The anomaly_detection_action_level configuration setting provides action
levels starting at 'Metrics only' for basic anomaly processing, and ending at 'IT Alerts' for
full processing and analysis.  
Action levels from lowest to highest:

Metrics Only
:   Only gather metrics from the data source without any further processing.

Bounds
:   'Metrics Only' processing level and in addition creates statistical model and show bounds
    in Insights Explorer.

Anomaly Scores
:   'Bounds' processing level and in addition calculates and display anomaly scores.

Anomaly Alerts
:   'Anomaly Scores' processing level and in addition creates anomaly alerts as
    applicable.

IT Alerts
:   'Anomaly Alerts' processing level and in addition creates IT alerts which are based on anomaly alerts, as applicable.
**Related tasks**   

* [Create a configuration settings rule](https://www.servicenow.com/docs/6kxDdt9Pd2xc3hNJKumvUg "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.")