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


---

# Self-health monitoring for Metric Intelligence

# Self-health monitoring for Metric Intelligence {#ariaid-title1}

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

Use Event Management self-health
monitors to monitor the health of Metric Intelligence infrastructure components and
processes, and to alert about potential issues. Self-health monitoring allows you to proactively
remediate issues and minimize data loss.
Metric Intelligence is pre-configured to use Event Management self-health monitors to
ensure that essential components and processes are functioning properly. If a monitor detects a
failure, then the Event Management
self-health monitoring system creates an event for the issue. These events are then converted
into an Event Management alert or get
appended to a previous alert. Metric Intelligence self-health monitors run every 60
seconds.

For example, if an Metric Intelligence MID Server distributed cluster experiences an
issue, an event is generated with the status of Major. Then, this event
is converted into an alert. Later, when the issue is resolved, a new event is generated with the
status of Info and the original alert is closed.

## Monitored components and processes {#self-health-monitoring-oi__section_ccs_bqm_kfb}

{#self-health-monitoring-oi__table_vhc_ltm_kfb__entry__2}

| Component/Process Check | Error Condition |
|-|-|
| Metric Intelligence extension is running properly | Monitor checks the status field of the ecc_agent_ext_context_metric table to detect a state of Error or Warning. |
| Metric Intelligence MID Server distributed cluster is running properly | Monitor checks the status field of the ecc_agent_cluster table to detect a state of Error, Segmented, orStopped. Note: For a state of Stopped, an event is created only if the error_message field is not empty. |
| Metrics are collected by active connectors that are configured for metrics collection | For each connector with the Metrics collection flag set to true: Monitor checks the status of the last_kpi_status field in the em_connector_instance table to detect a status of Error. |
| Essential Metric Intelligence scheduled jobs are active | Monitor checks the following essential scheduled jobs, to detect if any is inactive: * Metric Intelligence --- Metric configuration job * Metric Intelligence --- Sync tables with mid * Metric Intelligence --- Validate MID Distributed cluster {#self-health-monitoring-oi__ul_olg_3vm_kfb} |
[ ]

{#self-health-monitoring-oi__table_vhc_ltm_kfb}

For more information about enabling or disabling an Metric Intelligence self-health
monitor, see [Configure a self-health monitor](https://www.servicenow.com/docs/lak91wqXl1q1v~V_sV3waA "You can configure a self-health monitor to track Event Management components and see that they do not exceed the specified threshold.").
**Related concepts**   

* [Self-health monitors for Event Management](https://www.servicenow.com/docs/56B9Q0p6hweBtafCq3OOHw "Use the Event Management self-health monitors to track Event Management features and resolve issues.")  
**Related reference**   

* [Scheduled jobs installed with Metric Intelligence](https://www.servicenow.com/docs/fA0T6eH~9nxRqrlh6bODBQ "Several types of components are installed with activation of the Metric Intelligence (com.snc.sa.metric) plugin, including tables, scheduled jobs, and properties.")