--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Agent Client Collector for Visibility Content reference # Agent Client Collector for Visibility Content reference {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Review this information for details on OS query scripts, data collected, and definition of terms. ## OS module scripts for Agent Client Collector for Visibility Content (ACC-VC) {#agent-client-collector-for-visibility-references__section_i2q_lkz_z4b} These platform-specific plugins invoke platform-specific module scripts. Each script outputs to a standard JSON payload regardless of the platform. {#agent-client-collector-for-visibility-references__table_dnv_tzy_25b__entry__2} | Operating System family/plugin | Name of module script | |-|-| | Linux: acc-f-modules | basic_inventory.rb (Starting with ACC-F version 2.10.1, this will not be used.) | | Linux: acc-f-modules | data_collection.rb | | Linux: acc-f-modules | running_processes.rb | | Linux: acc-f-modules | tcp_connections.rb | | Linux: acc-f-modules | | | Windows: acc-f-modules | basic_inventory.rb (Starting with ACC-F version 2.10.1, this will not be used.) | | Windows: acc-f-modules | data_collection.rb | | Windows: acc-f-modules | running_processes.rb | | Windows: acc-f-modules | tcp_connections.rb | | macOS Operating Systems: acc-f-modules | basic_inventory.rb (Starting with ACC-F version 2.10.1, this will not be used.) | | macOS Operating Systems: acc-f-modules | running_processes.rb | | macOS Operating Systems: acc-f-modules | tcp_connections.rb | | Linux: acc-visibility-modules | installed_software.rb | | Linux: acc-visibility-modules | file_systems.rb | | Linux: acc-visibility-modules | storages_devices.rb (support for getting physical disk and corresponding disk partitions only) | | Linux: acc-visibility-modules | network_adapters.rb | | Linux: acc-visibility-modules | local_users.rb | | Linux: acc-visibility-modules | enhanced_inventory.rb | | Linux: acc-visibility-modules | cloud.rb | | Windows: acc-visibility-modules | installed_software.rb | | Windows: acc-visibility-modules | file_systems.rb | | Windows: acc-visibility-modules | storages_devices.rb (support for getting physical disk and corresponding disk partitions only) | | Windows: acc-visibility-modules | network_adapters.rb | | Windows: acc-visibility-modules | local_users.rb | | Windows: acc-visibility-modules | enhanced_inventory.rb | | Windows: acc-visibility-modules | cloud.rb | | Windows: acc-visibility-modules | sam_advanced.rb | | Windows: acc-visibility-modules | sam_processor.rb | | Windows: acc-visibility-modules | intel_ema.rb | | macOS Operating Systems: acc-visibility-modules | installed_software.rb | | macOS Operating Systems: acc-visibility-modules | file_systems.rb | | macOS Operating Systems: acc-visibility-modules | storages_devices.rb (support for getting physical disk and corresponding disk partitions only) | | macOS Operating Systems: acc-visibility-modules | network_adapters.rb | | macOS Operating Systems: acc-visibility-modules | local_users.rb | | macOS Operating Systems: acc-visibility-modules | enhanced_inventory.rb | | macOS Operating Systems: acc-visibility-modules | cloud.rb | [ ] {#agent-client-collector-for-visibility-references__table_dnv_tzy_25b} Note: running_processes.rb and tcp_connections.rb are interdependent. For an efficient Discovery, keep both tcp_connections.rb and running_processes.rb together. Both the files are needed to get the complete data. If one is not there, it will not populate the other data. To fetch information about all the running_processes on the macOS, you must provide sudo access to osquery. If this configuration is not made, then running_processes.rb will only fetch what is triggered by _servicenow user. For tcp_connections.rb, you must add 'sudo lsof' command in the sudoers file. If this is not done, tcp_connections.rb will only fetch what is triggered by _servicenow user. ## Data collected {#agent-client-collector-for-visibility-references__section_kcm_skz_z4b} ACC-VC uses the same classification criteria as IP-based Discovery for classifying as computer or server. The subset of collected data includes the following categories: * Basic inventory -- Starting with ACC-F version 2.10.1, this will not be used. * Data collection - Collects the necessary data for classification and identification of a host CI. This includes host name, serial numbers, and OS information. * Installed Software -- cmdb_sam_sw_install (if SAM enabled) and cmdb_software_instance (if SAM not enabled) * File Systems -- cmdb_ci_file_system * Storage Devices -- cmdb_ci_disk and cmdb_ci_storage_device * Serial Numbers -- cmdb_serial_number * Network Adapters -- cmdb_ci_network_adapter and cmdb_ci_ip_address * TCP Connections -- cmdb_tcp * Running Processes -- cmdb_running_process (ACC-VC also classifies the running processes and creates application CIs in cmdb_ci_appl, where possible) * Local User -- cmdb_os_user (Populates the local users for all the Operating Systems that ACC-VC supports by adding a new module called local_user) * Enhanced inventory -- Collects enhanced data (such CPU info, start_date, object_id) which is not necessary for identifying a unique host. {#agent-client-collector-for-visibility-references__ul_lgv_3jb_bpb} Figure 1. Relationships between host computer, file systems, and storage devices ## Agent Client Collector terms {#agent-client-collector-for-visibility-references__section_pnv_5kz_z4b} Agent Client Collector (ACC) : The software component installed on target hosts that communicates with the MID Server. Sometimes referred to as Agent. This component is a ServiceNow derivative of Sensu-Go. Agent Client Collector Framework (ACC-F) : A ServiceNow base scoped application that leverages ACC and provides core capabilities (including Check Types, Check Definitions, Policies, and so on) enabling other ACC scoped applications, including ACC-M and ACC-VC. Agent Client Collector Monitoring Monitoring (ACC-M) : A ServiceNow scoped application enabling monitoring use cases. Agent Client Collector for Visibility Content (ACC-VC) : A ServiceNow scoped application that implements push-based Discovery leveraging ACC and ACC-F. Horizontal IP-based Discovery : Traditional Discovery available to customers prior to ACC-VC. It discovers data via Probes and Patterns through the MID Server, requiring the Discovery Plugin. Modules : A subset of discovered data that is populated as part of Discovery. Examples of Modules include: Data Collection, Installed Processes, Serial Numbers, File Systems, Storage Devices, Network Adapters, Running Processes, and TCP Connections. Push-based Discovery : Discover data via ACC, ACC-F, ACC-VC, and the MID Server with a direct push of data from the target host. Discovery does not require specific IP range configuration on a Discovery Schedule or providing Discovery Credentials for target host. Sensu-Go agent : The Free and Open Source project which ACC is derived from. Virtual Machine Instance : A virtual target host running inside of a hypervisor, either on-premise or within a cloud service provider like AWS, GCP, or Microsoft Azure. Virtual Machine Image : A snapshot of a live virtual machine instance persisted to a file system or cloud storage.