Chat now with support
Chat with Support

Foglight for VMware 5.8.2 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

This 5.8.2 release of the Foglight for VMware accompanies the release of Foglight Evolve 9.2 and Foglight for Virtualization, Enterprise Edition 8.9.2. This release includes fixes for the following issues:

Defect ID



Fixed an issue that the service selector is not applied to VMware Environment Alarms page.

Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Defect ID

Known Issue


The Virtual Machines Network Performance - Service report is missing units when exported as an Microsoft Excel spreadsheet.


Too many vCenter sessions are detected, due to the agents not disconnecting properly when done. This leaves many idle sessions on the vCenter.


When forwarded, the vSphere Alarm Virtual machine CPU usage displays null values.


 vCenter alarms are not collected by default. To enable their collection, set the Alarms Collection Enabled property of the VMware Performance Agent to True.


A number of Warning messages are found in the log, indicating a big time difference between the monitored vCenter and Management Server.


Incorrect virtual CPU ratio values are found in custom reports.


The table on the Top CPU Consuming Virtual Machines view cannot be sorted.


VMware cartridge creates duplicate VMware Performance agents with the ID -1.


The vCenter Certificate's public key length has to be 1024-bits or higher and could not use MD5. This is because vCenters are configured to use a 512-bit long certificate keys. The Foglight Agent Manager JRE is updated to version (1.7u40) or higher, which restricts the certificate key length to 1024 bits or higher.


  1. Locate the following entry in the <fglam_home>/jre/lib/security/ file: 

    jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024

  2. Modify it as follows: 

    jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512

  3. Deactivate and activate the VMware Performance Agent.


The IP address of ESX host cannot be collected and presented in the dashboard.


If there are multiple virtual machines with the same name running in different virtual centers, their performance data may be incorrect.


Upgrading to Foglight for Virtualization, Enterprise Edition 8.0 causes the Virtual Environment Overview tiles to show zero objects.

Workaround: Update the VMware Performance agent on the VMware Environment Administration tab, as instructed. For upgrade instructions, see Upgrade and Compatibility.


When the IP or host name of the monitoring host changes, this results in two Virtual Center instances, one that collects data, and another that does not.
Workaround: Using the Data Management dashboard, navigate to VMware Model > Virtual Centers, and delete the Virtual Center host that no longer collects data.


After exporting the CPU Utilization graph to Excel, incorrect labels appear in the resulting file.


For large virtual infrastructure environments, the performance of the browser interface can be affected by the amount of memory allocated to the Java Virtual Machine (JVM) on the Management Server.

Management Server dashboards

Defect ID

Known Issue


On the All Hosts dashboard, accessible by clicking Homes > Hosts in the browser interface, Disk Current and Network Current columns for any ESX hosts or virtual machines show "n/a" instead of the actual metric values. This behavior does not apply to physical hosts collecting OS metric data. This table shows disk and network utilization percentages for ESX hosts or virtual machines which are not collected by  Foglight for VMware. Hovering over these columns shows the related disk and network throughputs, which appear in units other than percentages.

Workaround: There is no workaround available for this issue.


Third party known issues

Third party known issues

The following is an issue known to exist at the time of this release.

Defect ID

Known Issue


Performance metrics cannot be collected for VSAN 5.5 because of its limited API.
For more information, visit:

Workaround: Upgrade to VSAN version 6.0.


A known issue in vCenter 5.1, 5.5 and 6.0 leads to wrong packet loss values, causing the VMW Virtual Machine Packet Loss rule alarms to be triggered. For more information, visit:

Workaround: If you monitor version 5.1/5.5, install the latest patch. At the moment, there is no solution for version 6.0.


If a monitored VM is using a vmxnet3 adapter, networking data cannot be collected. This is a known issue in vCenter 6. For more information, visit:


The VM Network Performance data was lost when moving a virtual machine between vCenters.


The VMware Explorer displays logical disk information for RHEL 6 virtual machines, but not for RHEL 7 virtual machines. This is due to the limitation of the default open-vm-tools version 9.4.0, included with RHEL 7 and CentOS 7, which does not support the XFS file system.


vSwitch topology views display incorrect utilization and packet loss values, showing data for unused and standby NICs.
Workaround: Since NICs are connected physically, they receive broadcast messages, which results in the display of data transmission rates rate for these NICs. However there is no actual loss of data transmit. To prevent this data from appearing, physically remove such NICs.


The total command latency is collected for monitored datastores, but cannot be collected for NFS (network file system) storage.
Workaround: The total command latency is based on disk-based calculations, and is only available for a disk/LUN that uses SCSI commands. Not all types of datastores are disk-based (NFS for example is not), and sometimes a disk can create multiple datastores. As an alternative, the datastore total latency metric can be used.


The virtual machine guest OS boot time is only collected in vCenter 5 or higher.


Cluster CPU utilization is currently calculated using Hypervisor CPU usage. vCenter calculates the same values using only the available memory for virtual machines.


Collection of traffic type utilization metrics is only possible if vCenter network usage counters are available and configured properly. These metrics illustrate how different types of data traffic are represented in the overall network traffic managed by a virtual switch. In a default installation network usage counters (listed below) are set to 3. To enable the collection of traffic type utilization metrics, each of these counters must be set to 1:


On ESXi version 4.1 network usage counters are not available, so this feature is not supported.
ESXi versions 5.0 and 5.1 includes network usage counters, and they can be configured as required.
The counters were removed from ESXi versions 5.5, 5.5.0a, and 5.5.0b, so traffic type utilization metrics are not collected.

For more information, see the following article:


Upgrade and compatibility

Upgrade and compatibility

Foglight Evolve 9.2 and Foglight for Virtualization, Enterprise Edition 8.9.2 include a new version of Foglight for VMware 5.8.2. This new version of Foglight for VMware provides new capabilities to Foglight Evolve and Foglight for Virtualization, Enterprise Edition.

Foglight for VMware supports VMware vSphere and VMware vCenter Server versions 5.x and 6.x.

Important: The VMware Performance Agent uses a Virtual Center account to log in to the monitored Virtual Center. The administrative role associated with that account must be granted the Performance > Modify intervals privilege. When collecting traffic-type network metrics from the monitored ESX hosts, this privilege enables the VMware Performance Agent to change the performance metric counter levels in order to collect this data.


vCenters in Linked Mode: Linked Mode is supported, however an agent monitoring one vCenter does not gather data from other linked vCenters. Each vCenter requires its own dedicated agent.

The following version of the Cisco Nexus 1000V Switch for VMware vSphere is supported:

  • On vSphere 5.x, version 4.2(1)SV2(2.2) is supported. At the time of this release, this is the latest version of the Cisco Nexus 1000V Switch supporting vSphere 5.0, 5.1, and 5.5.

Note: The extended support for VirtualCenter 2.5 ended on May 21, 2013. Foglight for VMware is no longer tested with or supported for VirtualCenter 2.5. 

Foglight for VMware is not compatible with the VirtualCenter for VMware Server.

Important: If you install or upgrade to this version of Foglight for VMware on the Management Server (outside of the Foglight Evolve or Foglight for Storage Management product families), and you also have the Foglight for Storage Management cartridge installed on the server, you must ensure that the Foglight for Storage Management cartridge is at least version 3.1.4. Using an earlier version will prevent the Storage Management data collections and dashboards from working as expected.

The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version


Foglight Management Server


All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager


All platforms supported by this version of the Foglight Agent Manager

Foglight Evolve


All platforms supported by this version of the Foglight Evolve

Foglight for Virtualization, Enterprise Edition


All platforms supported by this version of the Foglight for Virtualization, Enterprise Edition

To upgrade to the latest version of Foglight for VMware:
  1. Deactivate all VMware Performance agent instances.
  2. On the Cartridge Inventory dashboard, install the following cartridge files. Do not remove the older version of these cartridges. Install version 5.8.2 over the older version.
  3. On the VMware Environment dashboard, on the Administration tab, update all of the existing VMware Performance agent instances.
  4. Important. If you increased the JVM memory allocation in a previous cartridge installation (as described in System Requirements), you need to repeat this process after deploying the new agent package and before activating the agents.
  5. Activate all VMware Performance agent instances.

Note: Extra minutes will be needed if you upgrade to the latest version in the environment where is deployed with more than 4,000 virtual machines.

For more information, see the Foglight Upgrade Guide.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating