new agent goes to silent mode immediately after discovery with breached threshold == 0 %DescriptionBefore any policies are getting synched to the agent, agent may run some on demand checks (mainly discovery) and in version 2.5.0 there's an issue with agent using a 0 % threshold for CPU utilization at that stage. The issue is fixed from version 2.6.0 and doesn't appear at versions prior to 2.5.0.Steps to Reproduce install new agent (with a brand new agent_id so that it will have a new record without a host ci on your instance).connect the agent to the instance.wait for disco to run.observe that agent is in silent mode (if you have event management, then observe that the event has the breached threshold set to 0. Otherwise, look at the agent log file for the statement containing the breached threshold).Workaroundif you encounter this issue with the 0 % threshold being breached, then this means your agent turned off data collection automatically before any policies has arrived to him. Please navigate to your agent on your instance and use the resume data collection ui action to reenable data collection and verify why discovery didn't run successfully (as discovery is usually the only check executed by the agent before any policies are synched to the agent and usually no policies are getting synched until the agent is discovered successfully).Related Problem: PRB1515469