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


---

# Agent Client Collector Framework reference

# Agent Client Collector Framework reference {#ariaid-title1}

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

Reference topics provide additional information about mapping and fine-tuning application services using Agent Client Collector Framework lists and forms.
* **[Agent Client Collector user roles](https://servicenow-prod.fluidtopics.net/r4U1GWhDNRgo0klOqY2zPw)**   
  Administrators can assign user roles to grant access to the Agent Client Collector. The following standard roles for the Agent Client Collector Framework (ACC-F) are included in the ServiceNow system with the Agent Client Collector installed on it.
* **[Agent Client Collector Framework default checks](https://servicenow-prod.fluidtopics.net/Lw92UpeJ_dzxlVskZGw93Q)**   
  Agent Client Collector Framework provides default checks with the base system.
* **[Agent Client Collector performance and footprint for URL monitoring](https://servicenow-prod.fluidtopics.net/_Ayt9NPkN3S~RhuQmlTcMg)**   
  The following tables display the agent performance KPIs and its footprint on the host during URL monitoring data collection execution on different operation systems.
* **[Agent Client Collector certificate revocation reasons](https://servicenow-prod.fluidtopics.net/h8iiEwHbl5Fk8yTjszu50A)**   
  The following table lists and describes the possible reasons for revoking an Agent Client Collector certificate to stop communication between the agent and ITOM cloud services.
* **[Agent Client Collector check definition page](https://servicenow-prod.fluidtopics.net/DNQs1Qxbzq7D841ai06ncQ)**   
  The fields to be configured on the Check Definition page, when creating a check definition.
* **[Agent Client Collector data collection properties](https://servicenow-prod.fluidtopics.net/ZwfdASjFAv3ZzeH5WiuL4Q)**   
  Description of the properties that determine the behavior of Agent Client Collector data collection.
* **[Agent Client Collector policy collection properties](https://servicenow-prod.fluidtopics.net/Iba096Sb_n9b5ljTQ~hBCw)**   
  Description of the properties that determine the behavior of Agent Client Collector policy collection.
* **[Agent Client Collector Framework configuration properties](https://servicenow-prod.fluidtopics.net/JuuaVzKeIn5e5IarG5kkgQ)**   
  Description of the properties that determine the behavior of Agent Client Collector Framework configuration.
* **[Agent Client Collector data collection tables](https://servicenow-prod.fluidtopics.net/VBsLpmlEOM2yyJwliu46gg)**   
  Agent Client Collector performs data collection based on the scoped apps that you've installed. Agent Client Collector Framework performs basic data collection, and Agent Client Collector for Visibility Content performs enhanced data collection.
* **[Account commands for LocalService, LocalSystem, and gMSA during Windows installation](https://servicenow-prod.fluidtopics.net/h5KFGMGc2zLiqj0Z4qCnOQ)**   
  When installing an agent on a Windows host using a LocalService, LocalSystem, or gMSA account, you must run msi commands to enable the accounts.
* **[Verify API is associated with a live agent](https://servicenow-prod.fluidtopics.net/VmIhqgjgHGrI0B1tfW6tCA)**   
  Call the AgentNowHandler.hasAgent API to determine if the CI is associated with a live agent. The API gets a sys_id of the CI and returns a true/false result.
* **[Configuration file options](https://servicenow-prod.fluidtopics.net/zq_E2TBTbSIGbIQLrAYa_A)**   
  Options available in the acc.yml configuration file.
* **[Synchronization properties for validating Agent Client Collector plugins](https://servicenow-prod.fluidtopics.net/U1XLKiqIcXmIBsmv3s7_vg)**   
  Use the following properties when synchronizing public certificates from the MID Server to the Agent Client Collector.
* **[ACC Error Task page](https://servicenow-prod.fluidtopics.net/vqoL9tHnY2Y9~Io52TMkPg)**   
  The fields to be configured on the ACC Error Task page.
* **[Agent Client Collector statuses](https://servicenow-prod.fluidtopics.net/rebPaGszYNYWJrF5EyurYg)**   
  The following table lists and describes the Agent Client Collector statuses.
* **[Agent Client Collector log levels](https://servicenow-prod.fluidtopics.net/IoRAdor8Hrlbg5tf9QkuKg)**   
  The following table displays the available log levels which indicate the severity of Agent Client Collector events.
* **[Agent Client Collector log rotation parameters](https://servicenow-prod.fluidtopics.net/PUlXUyl2LHmPLczdYcqLgQ)**   
  If Agent Client Collector logs get too large, they can drain system resources. To ensure system efficiency, configure parameters in the acc.yml file by which to rotate logs out of the system's storage (Windows default location = C:\\ProgramData\\ServiceNow\\agent-client-collector\\config\\acc.yml. Linux default location = /etc/servicenow/agent-client-collector/acc.yml).
* **[Agent Client Collector CPU protection thresholds](https://servicenow-prod.fluidtopics.net/xDp010JZ1RWwxSfEcmCMbQ)**   
  When an agent meets the configured thresholds specified in the agent's acc.yml file, it enters CPU protection mode, either for an individual check or for all checks. Agents in CPU protection mode appear in the agent logs with the syntax `Agent Protection`.
* **[Golden image structure and modularity](https://servicenow-prod.fluidtopics.net/x8bGs64kvx2ZSv4_iJYGTQ)**   
  The following table outlines the structure and modularity of the golden image mode for cloning agents, based on the operating system (OS) in use.
* **[Agent Client Collector health instance scan checks](https://servicenow-prod.fluidtopics.net/ALvuiMw_vdEaipbpZmf2FA)**   
  The Agent Client Collector (ACC) health instance scan suite includes checks that detect anomalies and issues on your instance. Use this reference to identify what each check does and when it applies.
* **[Agent onboarding configuration settings](https://servicenow-prod.fluidtopics.net/U6l1ucPFQEbLh_SHr0w~Ig)**   
  The settings you can customize when generating an Agent Onboarding installation plan. Toggle settings to activate and enable customization.
* **[Agent installation plan steps](https://servicenow-prod.fluidtopics.net/IfkgXF~K4ZgoQ5NxyMfwbA)**   
  After you complete agent onboarding, the system generates an installation plan. The following table describes each step in the plan and the commands or actions required.
* **[Agent Client Collector upgrade properties](https://servicenow-prod.fluidtopics.net/rEORgRNPifDAgjkiXg2KkA)**   
  System properties that control Agent Client Collector upgrade behavior, including the target version, rate limits, retry logic, and timeouts.
* **[Agent Client Collector upgrade error codes](https://servicenow-prod.fluidtopics.net/ZzwZnzo1YeZo_AcNw8YNPA)**   
  Error codes generated during Agent Client Collector upgrades, with descriptions and resolution steps.
* **[Supported platforms for Agent Client Collector auto-upgrade](https://servicenow-prod.fluidtopics.net/TIm5Yvb4iL3LYTBqrNR72w)**   
  Operating systems and package types supported for Agent Client Collector auto-upgrade, and the minimum agent version required.

