---
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


---

# Metric bounds sensitivity

# Metric bounds sensitivity {#ariaid-title1}

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

When measuring metrics in Insights Explorer, metric bounds may be overly sensitive,
creating an abnormally large number of anomalies. When this happens, the system adjusts itself to
ensure that fewer anomalies are created.

For example, if 95% of a CI's metric values fall within 2 standard deviations (STDs) of the mean metric values, those are considered sensitive bounds. Sensitive bounds generate a large number of anomalies, some
of which may be irrelevant. When sensitive bounds are detected, the system adjusts to measure metric values within 5 STDs, to generate fewer anomalies.

If sensitive bounds are not detected, (that is, 95% of metrics do not fall within 2 STDs of the mean metric value), the system measures metric values within 3 STDs. Any metric values falling outside the configured bounds become
anomalies.

The previous values are set by default. For details on customizing these values, see [Sensitivity bounds properties for Insights Explorer metrics](https://servicenow-prod.fluidtopics.net/DMsbKPJ4BliP_k5yj6xinA "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).").