Agent Client Collector Data Collection is "Off (auto)" with "data collection has been stopped due to high CPU usage"Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } A new or existing Agent record has Data Collection = Off (auto). Event Monitoring's Self-Health Monitoring may create an Alert "Agent_XXXX data collection has been stopped due to high CPU usage that reached the 0 percent threshold. For information on which checks consume high CPU, locate messages with the string "Agent Protection" in the agent log." The "Recent ECC Queues" related link on the agent's form will list MonitoringProbe ECC queue jobs for this agent, and the input payload for the [ { "client" : "XXXX", "agent_id" : "744876d452a192cc", "check" : { "interval" : 0, "timeout" : 0, "output" : "{\"silent\":true,\"cpu_threshold_breached\":0}", "status" : "0", "priority" : "0", "check_type_id" : "00425b415bc300106fa3262fb681c7ff" }, "timestamp" : 1631616769 The acc.log file on the host will confirm this: {"component":"agent","level":"info","msg":"Agent Protection: init agent protection with the following settings: cpu threshold : cpu Limit: 5 proxy cpu Limit: 15 monitorInterval: 60 interval: 3 ;OS Cpu num: 8","time":"2021-09-14T12:18:49+02:00"}...{"component":"agent","level":"info","msg":"Agent Protection: cpu exceeded the limit of 0%; agent total checks cpu: 0 monitor #1","time":"2021-09-14T12:50:49+02:00"}{"component":"agent","level":"info","msg":"Agent Protection: List of highest cpu checks : ","time":"2021-09-14T12:50:49+02:00"}{"component":"agent","level":"info","msg":"Agent Protection: cpu exceeded the limit of 0%; agent total checks cpu: 0 monitor #2","time":"2021-09-14T12:51:49+02:00"}{"component":"agent","level":"info","msg":"Agent Protection: List of highest cpu checks : ","time":"2021-09-14T12:51:49+02:00"}{"component":"agent","level":"info","msg":"Agent Protection: cpu exceeded the limit of 0%; agent total monitored cpu: [0 0 0] ;monitor #3 ;Turning off data collection","time":"2021-09-14T12:52:49+02:00"}Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ACC is very careful not to impact the available CPU on the hosts it is installed on, and deliberately turns off collection if CPU percentage used goes above a set amount, which by default is 5% CPU usage. This is checked every 60 seconds, and if 3 in a row fail, then Data collection is automatically stopped.Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The parameters for the CPU check can be modified if necessary, per-agent, in the acc.yml configuration file on the host. On Windows this is in C:\ProgramData\ServiceNow\agent-client-collector\config. Details of the parameters to modify are in the docs:Agent Client Collector CPU protection thresholds (Rome) The relevant section of the file of a new install of ACC-F 2.5 looks like this: # Defines the threshold for agent CPU usage. If threshold is exceeded, data collection will be turned off.agent_cpu_threshold: cpu_percentage_limit: 5 # CPU percentage limit. Default = 5. repeated_high_cpu_num: 3 # Number of consecutive times the CPU percentage limit must be exceeded. Default = 3. monitor_interval_sec: 60 # Indicates that the monitor will run every X seconds. Default = 60. agent_cpu_threshold_disabled: false # Indicates whether gathering CPU threshold values for the agent protection feature is disabled. proxy_cpu_percentage_limit: 15 # CPU percentage limit when agent is running proxy check(s). Default = 15 To edit that file: Logged into the host, as an administrator edit the acc.xml file on the host, increasing the value of cpu_percentage_limitSave From the instance, on the Agent form: click "Restart agent" on the agent's form.From the instance, click "Resume data collection" on the agent's form. You can confirm the agent is now using the new settings from the acc.log file if you wish: {"component":"agent","level":"info","msg":"Agent Protection: init agent protection with the following settings: cpu threshold : cpu Limit: 50 proxy cpu Limit: 15 monitorInterval: 60 interval: 3 ;OS Cpu num: 8","time":"2021-09-14T13:43:38+02:00"}