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


---

# Configuring Metric Intelligence

# Configuring Metric Intelligence {#ariaid-title1}

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

Plan and configure your Metric Intelligence implementation.

## Configuration overview {#configuring-metric-intelligence__cf-config-parent-checklist}

Metric Intelligence configuration typically follows these steps:

1. Install the AIOps Experience plugin \[sn_sow_aiops\].
2. [Manually configure a MID Server for Metric Intelligence](https://servicenow-prod.fluidtopics.net/soz3EUl_XxpXDwt2PhhpdQ "To use Metric Intelligence, configure at least one MID Server with Metric Intelligence as a supported application, with the Metrics capability, and which runs the Metric Intelligence Metrics extension. Then, add that Metric Intelligence MID Server as a member to a MID Server distributed cluster.").
3. [Activate Metric Intelligence](https://servicenow-prod.fluidtopics.net/qtPvMJKm2Abj5TshDZdMig "Metric Intelligence enables you to capture, explore and analyze operational metrics data, identifying and indicating anomalies. This analysis can prevent potential service outages.").
4. [Stream metrics to the instance, via the relevant data source or connector](https://servicenow-prod.fluidtopics.net/a~EMaZ1m0j3uw_e4yllpqQ "When setting up Metric Intelligence, you must configure a source for metric collection. Metric collection can be performed either by the Agent Client Collector, or by metric connectors.").
5. [Choose and configure metrics to monitor](https://servicenow-prod.fluidtopics.net/TeSckDnQjs0TeuDpJai2Og "Metric Intelligence uses data sources that can be monitoring hundreds of metrics for all CIs. Choose for each data source type which details are important for which CIs, and then activate or deactivate the respective monitor type to control the amount of data that is being processed.").
6. [Ensure that metrics are properly bound to CIs](https://servicenow-prod.fluidtopics.net/by_1zowEeXdGDWzuLMiTAQ "Bind metrics to resources to simplify metric events binding by enabling binding to resources such as specific disks or web pages, in addition to binding to CIs.").
7. [Configure the action level for anomaly detection](https://servicenow-prod.fluidtopics.net/qfRyESwgFOvjl2fNpArMYg "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.").
8. [Define an advanced promotion rule, to determine the conditions for promoting an anomaly alert to an IT alert](https://servicenow-prod.fluidtopics.net/e8wyxEkZPis7V2Zgjusbjg "Create a definition for the Advanced Promotion Engine so that you can define the conditions for promoting the anomaly alerts to IT alerts. By promoting the alerts that meet the conditions, only the most relevant alerts move to the table.").
{#configuring-metric-intelligence__cf-config-parent-tasks-ol}