Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Exploring Agent Client Collector Monitoring

Agent Client Collector Monitoring is built on a Sensu framework which enables you to adopt and extend monitoring checks from the community. Agent Client Collector Monitoring collects data on your company’s infrastructure and installed applications.

Agent Client Collector Monitoring overview

Checks and policies run on the agent’s client to retrieve the relevant data, which is transformed into events or metrics, as appropriate. Events and metrics are sent from the agent to your ServiceNow instance through a Metric Intelligence MID Server and are stored in the relevant database. A single MID Server can support multiple agents (such as ACC-M and ACC-L). For details on configuring the MID Server for Metric Intelligence, see MID Server distributed cluster for Metric Intelligence.

Agent Client Collector Monitoring comes with the Event Management plugin and also requires installing the request Metricbase (Clotho DB), as described in How to request Metricbase (Clotho DB) configuration (KB0816088).

For details on the plugins installed with Agent Client Collector Monitoring, see Plugins or applications installed with ITOM AIOps.

Agent Client Collector Monitoring workflow

The following illustration describes the layout and data flow within the Agent Client Collector Monitoring application.

Image omitted: acc-m-infographic.png
ACC-M Infographic

Agent Client Collector Monitoring benefits

BenefitFeatureUsers
Monitor logs which track events occurring in a Windows environmentWindows event log monitoringAgent Client Collector administrator
Monitor operating systems and applicationsOperating system and application monitoring using Agent Client CollectorAgent Client Collector administrator
Gather metrics on host dataMetric IntelligenceAgent Client Collector administrator