StratoProbe collection methods

This page describes the collection methods available in StratoProbe, and the types of data that StratoProbe collects from your infrastructure.

Collection methods

Depending on your asset type, StratoProbe 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, StratoProbe collects only certain types of data. This section describes what data StratoProbe 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

Data not collected

Depending on the security level you choose for collection, some data is replaced with placeholder values before being sent to StratoZone. For more information, see Security levels.

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

What's next