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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Limit metrics collection and evaluation

# Limit metrics collection and evaluation {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can limit the metrics you send from the MID Server to the
instance, either by de-activating a specific CI or an entire CI type.

## Before you begin

Role required: agent_client_collector_admin

## Procedure

1. To limit metrics collection and evaluation for specific CIs:
   1. Navigate to Event ManagementAnomaly DetectionMetric to CI.  
      The Metric to CI Mappings page appears.Figure 1. Metric to CI Mappings   

      Note:  
      The Metric to CI Mapping is identified by both its metric identifier and its configuration item.
   2. To prevent sending metrics for a specific metric and CI, set the value of the Active column to false.
   {#acc-limit-metrics-collection__substeps_jcv_xdl_vnb}
2. To limit metrics collection and evaluation for an entire CI type:
   1. Navigate to Event ManagementAnomaly DetectionMetric Types.  
      The Monitoring System Metric Types page appears.Figure 2. Monitoring System Metric Types   

   2. To prevent sending metrics for a metric type, set the value of the Active column to false.
   {#acc-limit-metrics-collection__substeps_kss_cgl_vnb}

*[\>]: and then