Agent Client Collector configuration data files

  • 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 Configuration Data Files

    Configuration data files are essential for storing dynamic instance data, such as virtual machine details, which are used during the execution of checks by the Agent Client Collector. This functionality ensures that checks are performed using up-to-date and accurate information about the monitored instances.

    Show full answer Show less

    Key Features

    • Attachment Based: Each configuration data file contains a single attachment with instance-specific data.
    • Synchronization: Modifications to attachments are synchronized across all MID Servers, ensuring consistency. Deleted files and attachments are also removed from the MID Servers.
    • Access Point: Configuration data files can be accessed on the MID Server at static/cache/config-files.
    • Size Limitation: Configuration data files must not exceed 10MB.
    • Check Definitions: Individual checks, termed check definitions, utilize configuration data files to execute accurately against monitored systems.
    • Domain-Specific Synchronization: Files are synchronized only within the same domain for secure data handling.

    Key Outcomes

    Using configuration data files enables ServiceNow customers to:

    • Store Relevant Data: Store instance-specific data necessary for checks, ensuring they run with the most current information.
    • Create Effective Checks: Develop check definitions linked to configuration data files for accurate monitoring of system metrics.
    • Maintain Data Consistency: Automatically synchronize updates across all relevant MID Servers for reliable data availability.
    • Efficient Execution: Ensure that checks are executed using the latest instance data, improving overall monitoring performance.

    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/cache/config-files.
    • 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.