---
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 Agent Client Collector Monitoring

# Configuring Agent Client Collector Monitoring {#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 Agent Client Collector Monitoring implementation.

To configure Agent Client Collector Monitoring, follow these steps:

1. [Configure a MID Server to work with Agent Client Collector Monitoring](https://servicenow-prod.fluidtopics.net/neLuF0Se1EHed4VTsHasDQ "Connect agents to a MID Server to enable Agent Client Collector Monitoring functionality.").
2. [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.").
3. [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.").
4. [Create a configuration settings rule](https://servicenow-prod.fluidtopics.net/6kxDdt9Pd2xc3hNJKumvUg "Configuration settings affect how metric data is processed. Configuration settings rules override the default metric processing behavior to determine the system actions when an anomaly is detected.").
5. [Enable metrics collection and evaluation](https://servicenow-prod.fluidtopics.net/L4lOXcLqxLJj8EThL9~hrQ "To enable a ServiceNow instance to collect and evaluate metrics, you must create a distributed MID Server cluster, associate MID Servers with the cluster, and enable Metric Intelligence for your MID Server.").

{#configuring-agent-client-collector-monitoring__ol_shx_bgt_x1c}

Depending on the checks and metrics you want to monitor, perform the following actions to enable full check activation and metrics collection:

1. [Enable viewing HAProxy metrics](https://servicenow-prod.fluidtopics.net/4hJPn1JA6KBp~iqXI66ORg "Configure the HAProxy metrics stats page to enable monitoring your system devices by viewing HAProxy metrics.").
2. [Enable running of Varnish checks](https://servicenow-prod.fluidtopics.net/6ZtCM27WmMRlzZ_z50G8jQ "Use application fingerprints to discover the Varnish CI, to enable running Varnish checks.").
3. [Select the Azure policies to activate for metric collection](https://servicenow-prod.fluidtopics.net/I~ZprnShslqpbAgNmniV0g "Activate the Azure policies that come with the Agent Client Collector base system so that Azure virtual machines can collect metrics. These metrics help you monitor the configuration items (CIs) in the CMDB.").
4. [Create Azure policies for metric collection](https://servicenow-prod.fluidtopics.net/uumOhEo6jIKgpGW~vwfK7A "Create your own policies to enable Azure to collect the metrics for the resources that have policies that don’t come with the base system. The Azure Metrics Collector check brings the metrics to the agent through the Azure Metrics Batch API.").
{#configuring-agent-client-collector-monitoring__ol_zmz_pgt_x1c}