Pure1 VM Analytics Collector Version 3.7.0

Release Notes for VMware Solutions
Audience
Public
Content Type
Release Notes
Technology Integrations
VMware
Source Type
Documentation

Collector Requirements

See the Everpure VMware Appliance Quick Reference. Additional requirements are as follows:

  • The IP addresses of the vCenter servers to collect from and network access to these vCenter servers.

  • A username/password for the vCenter servers being collected from, with at minimum read-only access.

  • VM Analytics Collector can collect from vCenter servers version 5.5 and higher.

  • The VMware Appliance and Collector must have Phonehome enabled. This requires the Appliance and Collector to have network/firewall access to Pure1.

  • VM Analytics supports VMFS, vVols, vSAN, and NFS datastores.

  • VMware Tools 10.1+ must be installed in VMs for Pure1 to calculate VM capacity metrics.

New Features

  • Added the Download CSV button to the Pure1 Virtual Machine Topology.

  • Added Virtual Machine metrics and information topology:

    • VM.GuestInfo.guestFamily

    • VM.GuestInfo.guestFullName

    • VM.GuestInfo.guestState

    • VM.GuestInfo.net

    • VM.GuestInfo.toolsStatus

    • VM.Config.hardware.device

Note: The new added metrics and information are used in the Assessment page.

Enhancements

  • Changed the CPU metric collection from per logical core usage to total CPU usage. For more information, follow this article.

  • Added explicit information for registration error code 5: "appliance already registered".

VM Analytics Update: Host CPU Metric

What has changed?

VMware offers hyperthreading support, which introduces the concept of logical cores.

In a typical configuration, hyperthreading doubles the number of cores, resulting in 12 physical cores corresponding to 24 logical cores.

vSphere provides both physical and logical core counts, plus the utilization metric per core or total CPU.

Previously, the VM Analytics collector utilized the ‘cpu.usage.average’ metric endpoint for each logical core, aggregating all core usage to provide the total CPU utilization metrics.

To align with the vSphere CPU utilization charts, VM Analytics needs to aggregate per physical core or ideally leverage the total CPU usage metric directly provided by the vSphere API.

What has been impacted?

  • VM Analytics: Host CPU utilization will effectively increase to match the vSphere CPU utilization charts.

  • Virtualization Assessment: The per-core cost analysis feature is driven by the number of physical cores and total host CPU utilization; therefore, the license and potential saving cost will be reduced.