Agent Client Collector Monitoring

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Agent Client Collector Monitoring

    Agent Client Collector Monitoring allows you to oversee service availability and assess the health and performance of your environment, ensuring that your infrastructure and applications operate effectively. It is essential for maintaining optimal performance and preemptively identifying any issues.

    Show full answer Show less

    Key Features

    • CPU Protection Mode: Activated when CPU consumption is high, preventing checks from running. This mode requires user intervention to resume data collection.
    • Monitoring Setup: Instructions available for enabling monitoring on the MID Server.
    • Metric Intelligence: Tools to analyze metric data and detect anomalies in performance.
    • Monitoring Technology Dashboard: Provides insights into server resources by platform.
    • Proxy Agents: Enables health and performance monitoring of Configuration Items (CIs) deployed outside the host server.

    Key Outcomes

    By utilizing Agent Client Collector Monitoring, you can ensure that your services remain available and performance is optimized. The application helps in proactively identifying problems, managing resource consumption, and facilitating troubleshooting through community support and known error resources.

    Agent Client Collector Monitoring enables you to monitor your service availability, examine the health and performance of your environment, and ensure that your infrastructure and its applications are running properly.

    Get started

    Note:

    If checks are not running on the agent's devices, your agent may be in CPU protection mode. CPU protection mode is activated automatically when a device's CPU consumption is too high for one of two reasons: either the user is running too many checks, or the machine is under-resourced. When it happens, the agent's Data Collection status turns to Off. ACC-F generates an event and records it in a log. To manually resume data collection by the ACC agent, see Pause Agent Client Collector data collection.

    The user needs to monitor the activity of the ACC to resolve the issue through manual intervention and then re-enable ACC collection. To setup the ACC monitoring, see Enable Agent Client Collector monitoring on the MID Server.

    Troubleshoot and get help