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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Metric bounds sensitivity

# Metric bounds sensitivity {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Insights Explorer automatically widens metric bounds when too many anomalies are detected, reducing false alerts so you can focus on genuinely important issues.

Reducing the number of anomalies enables you to focus on genuinely important issues while eliminating irrelevant anomalies.

The system uses measurement ranges, called 'bounds', to determine what is considered normal and abnormal metric behavior. These bounds are calculated automatically from your historical metric data.

## About variation ranges {#metric-bounds-sensitivity__section_r2d_qy5_g3c}

A variation range is a measurement of how much your metric values typically vary from their average. The system calculates variation ranges automatically by analyzing your historical data. For example, if your CPU usage averages 50%:

* A small variation range (like 2%) indicates that values stay consistent, typically between 48-52%.
* A large variation range (like 10%) indicates that values fluctuate more widely, typically between 40-60%.
{#metric-bounds-sensitivity__ul_yvd_wnq_1kc}

## How bounds are set {#metric-bounds-sensitivity__section_hhm_nz5_g3c}

The system sets bounds by measuring how far away from the average a value can be before it's considered abnormal. The formula is: `Average +/- (multiplier x variation range)`.

The multiplier is a number that controls how wide or narrow the acceptable range is.

* Smaller multipliers create narrower bounds and detect more anomalies.
* Larger multipliers create wider bounds and detect fewer anomalies.
{#metric-bounds-sensitivity__ul_opb_qbv_g3c}  

## CPU averages 50% and the standard deviation is 5% {#metric-bounds-sensitivity__example_obl_xdv_g3c}

{#metric-bounds-sensitivity__table_m4y_b2v_g3c__entry__2}

| Multiplier | Bounds |
|-|-|
| 2 | 40% to 60% (50%+/-10%) |
| 3 | 35% to 65% (50%+/-15%) |
| 5 | 25% to 75% (50%+/-25%) |
[Table 1. Metric bounds]

{#metric-bounds-sensitivity__table_m4y_b2v_g3c}

## Automatic adjustment process {#metric-bounds-sensitivity__section_rvq_q2v_g3c}

1. High sensitivity detected: If 95% of a CI's metric values fall within a multiplier of 2, the system recognizes this as overly sensitive. As a result, too many anomalies are created, including some that aren't actually problems.
2. The system widens the bounds: When high sensitivity is detected, the system automatically adjusts from a multiplier of 2 to 5, creating wider bounds and generating fewer, more meaningful anomalies.
3. Normal sensitivity: If high sensitivity isn't detected, the system uses a multiplier of 3 for moderate bounds.

{#metric-bounds-sensitivity__ol_zw4_t2v_g3c}

Any metric values falling outside the configured bounds are tagged as anomalies.

The multiplier values (2, 3, and 5) are set by default. For details on customizing these values, see [Sensitivity bounds properties for Insights Explorer metrics](https://www.servicenow.com/docs/gUw~9ZfLaSXa7gcKtO_cPQ "The following properties can be configured to customize system behavior when detecting sensitive bounds for Insights Explorer metrics. To invoke changes to the default values, navigate to System Properties > All Properties and add the indicated properties (they are not visible by default).").