Data collected from VM managers and user requirements

Edit online

Review the types of data that the VM Manager Tool collects from VM managers and requirements for the user that is used to connect to the VM managers.

User requirements

The minimal requirement for the user that is used to connect to VM managers is the read-only access to all VMs on which the scanner is installed and their hosts. However, it is recommended to define a user that has access to all hosts in your environment in case a VM is migrated between hosts.

Data collected from VM managers

The following data is collected by the VM Manager Tool.
  • On the cluster level
    • uuid
    • name
  • On the host level
    • uuid
    • name
    • serial_number (optional)
    • cores_count
    • active_sockets_count
    • cpu_model
    • hardware_vendor
    • hardware_model
  • On the VM level
    • uuid
    • hostname (optional)
    • vp_count

Data collected from VMware vSphere

The following data is collected from VMware vSphere™ by using its REST API. The data is then mapped into generic data that is sent to the License Metric Tool server.
Table 1. Data collected from VMware vSphere
Object Property Comment
HostSystem name
vm
hardware.systemInfo.uuid
hardware.systemInfo.vendor
hardware.systemInfo.model
hardware.systemInfo.otherIdentifyingInfo Value collected optionally to obtain the server serial number.
hardware.cpuPkg
hardware.cpuInfo.numCpuPackages
hardware.cpuInfo.numCpuCores
runtime.connectionState
VirtualMachine name
config.uuid
guest.ipAddress
runtime.powerState Value collected to skip VMs that are not running.
config.hardware.numCPU
config.ftInfo.role Value collected to skip VMs with fault tolerance enabled.
config.template Value collected to skip VMware templates.
ClusterComputeResource name
host
Folder childEntity
childType
Datacenter name
hostFolder