Agent Client Collector configuration data files

  • Release version: Yokohama
  • Updated September 17, 2025
  • 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 configuration data files

    Agent Client Collector (ACC) configuration data files store dynamic, instance-specific data—such as virtual machine details—that check definitions use during execution. This enables checks to run with the most current and accurate information about the monitored instances, ensuring precise and reliable monitoring outcomes.

    Show full answer Show less

    Key Features

    • Attachment-based structure: Each configuration data file contains a single attachment holding instance data, for example, Azure VM details.
    • Synchronization across MID Servers: When an attachment is added, updated, or deleted, the data file synchronizes automatically across all MID Servers configured with ACC, maintaining data consistency.
    • Domain-specific synchronization: Files synchronize only with agents within the same domain, supporting secure and localized data handling.
    • Size limitation: Configuration data files cannot exceed 10MB, ensuring efficient storage and transfer.
    • Check definition association: Each check definition is linked to a configuration data file, allowing agents to download the relevant data file needed to execute a specific check.
    • Storage location: Data files are stored on the MID Server under the \static\accconfig directory (or static/cache/config-files), facilitating easy access and management.

    Practical Application for ServiceNow Customers

    By leveraging ACC configuration data files, ServiceNow customers can ensure that their monitoring checks—such as CPU usage or system status—are executed with up-to-date environment-specific data. This dynamic data storage and synchronization approach helps maintain accurate monitoring across distributed MID Servers, improving operational awareness and response.

    When configuring ACC checks, customers should associate relevant configuration data files with their check definitions to guarantee that agents download the correct data during execution. Additionally, understanding the synchronization behavior helps manage data consistency across MID Servers within the same domain.

    Configuration data files store dynamic instance data, such as virtual machine details, that check definitions use during execution. This ensures that checks are executed with up-to-date and accurate information about the instance being monitored.

    Configuration data files structure

    • Attachment based: A configuration data file contains a single attachment with instance data, such as Azure VM details.
    • Synchronization: When an attachment is added or deleted, the data file is synchronized across all MID Servers configured with the Agent Client Collector. If a file or its attachment is deleted, it is also removed from the MID Server.
    • Access point: The configuration data files can be accessed on the MID Server at \static\acc_config.
    • Size: Configuration data files cannot be larger than 10MB.

    Check definitions used by configuration data files

    • Check definition: Individual check entries are referred to as check definitions. For instance, os.linux.check-system-cpu checks the CPU on Linux systems.
    • Accessing check definitions: Check definitions can be accessed from All > Agent Client Collector > Configuration > Check Definitions.

    File association

    • Download process: When a check executes, the agent downloads the configuration data file associated with that check.
    • Domain-Specific Synchronization: Files are synchronized only with agents within the same domain, ensuring secure and localized data handling.

    Working with configuration data files

    Configuration data files serve as a repository for dynamic instance data that is used by check definitions when they are executed. These files ensure that checks are run with accurate, real-time information about the systems or instances being monitored. Configuration data files work as follows:
    • Store instance-specific data: Configuration data files store dynamic instance data, such as virtual machine details, server configurations, and other system-specific information. This data is used by check definitions during execution to ensure the latest information is available.
    • Create check definitions: A check definition is created with an associated configuration data file. For example, a check definition monitoring system CPU data may include configuration data detailing the system's environment, ensuring checks use accurate and relevant instance data.
    • Synchronize with MID Servers: When a configuration data file is added or updated, it synchronizes across all MID Servers communicating with the Agent Client Collector. If the file or attachment is deleted, it is also removed from the MID Servers, ensuring consistency and up-to-date data availability.
    • Execute with updated data: During execution, the Agent Client Collector agent downloads the relevant configuration data file from the MID Server. The agent uses this data to execute the check, ensuring access to the most current and accurate instance information.
    • Store and access data: Configuration data files are stored on the MID Server in the static/cache/config-files directory. This storage location facilitates easy access and management, ensuring the necessary data for checks is always available when needed.