This page describes the collection methods available in discovery client, and the types of data that discovery client collects from your infrastructure.
Collection methods
Depending on your asset type, discovery client supports three types of methods that you can use to collect data:
- OS scan: Use this method to collect data from servers or VMs with Windows or Linux operating systems.
- vSphere scan: Use this method to collect data from VMware assets where OS scan cannot run.
- Database scan: Use this method to collect data from databases.
For more information about the requirements your assets must fulfill, see Requirements for machines and databases scanned.
Types of data collected
Depending on the collection method you choose, discovery client collects only certain types of data. This section describes what data discovery client collects from your assets.
OS scan
Data collected
- Machine information as reported by OS, such as CPU, memory, and disk space
- Software and, only for Windows assets, services installed on the asset
- Machine performance data, such as CPU and memory utilization, disk IOPS, and network transfers
- Machine dependency data
- MS SQL Server instance and version
vSphere scan
Data collected
- Machine information as reported by OS, such as CPU, memory, and disk space
- VMware folder path
- VMware VM ID
- VMware vCenter URL
- Machine performance data, such as CPU and memory utilization, disk IOPS, and network transfers
Data not collected
- Software and services installed on the asset
- Machine age based on the underlying BIOS data
- Machine network dependency data
- Installed databases' instance and version information
Database scan
Data collected
- Database and instance name
- Database version and edition
- Database sizing information, such as disk size and usage, and CPU and memory utilization
- Table and database metrics
- Feature and patch installation
- Clustering enabled
- Configuration file path names
- Global variables
- Index information
- Names of procedures, functions, and events
Data not collected
- Database or other user or account data
- User-created table content
- Database code such as stored procedures, functions, and views
Technical logs
After you opt in to the online discovery, the discovery client sends technical logs and error messages to Cloud Logging, where they are stored for debugging purposes. If you ever experience issues, the Google Cloud support teams might be able to access the logs to help you with troubleshooting.
When you use the discovery client in offline mode, it doesn't send any technical logs to Cloud Logging.
What's next
- Learn more about the requirements for machines and databases from which you want to collect data.