Chat now with support
Chat with Support

Foglight for VMware 5.8.2 - Release Notes

System requirements

System requirements

Before installing Foglight for VMware, ensure your system meets the following minimum hardware and software requirements:

Operating System

Foglight for VMware can be installed on any supported Foglight Management Server configuration.

Platform, Memory and Hard Disk Space The platform, memory, and hard disk space requirements for the monitored servers must match the Agent Manager requirements. For complete information, see the System Requirements and Platform Support Guide.

Note: 32-bit Windows and Linux Agent Manager installers are not included in the Foglight Evolve installer. New installations should use 64-bit Agent Managers. If you are upgrading 32-bit agent hosts, you can obtain 32-bit Agent Manager Installers from Quest Support.

For a complete list of system requirements, refer to the Installing the Virtualization Management Capabilities guide.

VMware Performance Agent and Agent Manager configuration

On 64-bit hosts meeting the minimum system requirements, the embedded Agent Manager can be used to run VMware Performance Agents to monitor up to1000 virtual machines. If the total number of virtual machines to be monitored from a single agent host is greater than 4000, an Agent Manager should be installed on a separate host.

Important: Foglight Evolve Virtual Appliance comes pre-configured to support up to 4,000 virtual machines. If you are using this product, there is no need to follow the configuration procedure described in this section.

If additional cartridges and agents are added to the environment, product performance should be monitored and agents moved off of the embedded Agent Manager to reduce the load.

Foglight VMware Performance Agent host system requirements

  Minimum CPU Minimum Memory Minimum Host Memory Total Monitored VMs
Windows 64-bit


2 GB

4 GB


Linux 64-bit


2 GB

4 GB


* Additional CPUs may be required for larger environments.

Monitoring more than 4000 virtual machines from a single agent host

The Agent Manager JVM usually requires additional memory to monitor more than 4000 virtual machines. The total number of virtual machines is the total from all vCenters that will be monitored from all VMware Performance agents running on the Agent Manager.

The following calculations are guidelines, not hard and fast rules. Memory requirements can vary greatly from installation to installation with similar VM counts. If insufficient memory is configured, the failure mode is easily recognizable: all agents on the Agent Manager host will go into a broken state after the agent(s) were activated for a short period of time, usually within 24 hours. In addition, the Agent Manager log will contain a line similar to the following:

Caused by: java.lang.OutOfMemoryError: Java heap space

If this is the case, add memory greater than what is shown in the calculations below, in increments of 512 MB until the agents stabilize.

JVM memory requirements for VMware Performance agents are calculated using the following formula:

512 MB + 0.5 MB/VM

According to the above formula, monitoring 4000 virtual machines requires 2512 MB of memory:

512 MB + 2000 MB = 2512 MB (round up to 3 GB)

he default setting for agents deployed on 64-bit systems is 2560 MB, which suffice this environment.

Similarly, monitoring 8192 virtual machines requires 4608 MB of memory:

512 MB + 4096 MB = 4608 MB

Foglight Evolve Virtual Appliance comes pre-configured to support up to 4,000 virtual machines. This requires the default Agent Manager settings to be changed.

To change the JVM memory settings:
  1. Determine the amount of additional memory required. This will be the total from the last step above minus the default value of 2560 MB. In the example above, this is 4608 – 2560 = 2048 MB.
  2. On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory.
  3. Add the following lines in the Memory Settings section:

    vmparameter.0 = "-Xms2048m";
    vmparameter.1 = "-Xmx2048m";

    Note: If this file has been previously edited, increment the numeric parameters accordingly.
  4. Delete the existing deployed negotiation configuration settings directory:

  5. Restart the Agent Manager for these settings to take effect.
Host system recommendations

When monitoring larger vCenters, the Agent Manager machine hosting the VMware Performance agents should be dedicated to this task. No other Foglight agent types should run on the host and the host should not run any other applications.


Regardless of the values set for JVM memory above, Agent Manager never allocates more than 80% of system memory. So the machine hosting the Agent Manager and VMware Performance Agents must have sufficient memory. Beyond the memory requirements of the Agent Manager, a minimum of 2 GB should be free for the operating system. In the example above for 8000 VMs and an Agent Manager memory requirement of 4608 MB, the host should have a minimum of 6656 MB - the greater of:

1.25 x 4608 MB = 5760 MB


2048 + 4608 MB = 6656 MB

If the Foglight Agent Manager is configured on a virtual machine, it is recommended that the VM use a memory reservation to ensure maximum performance.


CPU usage on the Agent Manager host is relatively low most of the time. However, usage peaks dramatically during the performance metric collection. This is normal and expected. CPU utilization consistently over 50% is an indication that additional processing power is required. As with memory, usage can vary between different installations with similar numbers of virtual machines. The following guidelines should be followed:

Up to 1000 VMs

2 CPUs

1000 – 4000 VMs

4 CPUs

4000+ VMs

add 1 CPU per 1000 VMs – round up when necessary


When the Agent Manager and VMware Performance agents are running on a virtual machine, the VM should be configured with CPU reservation whenever possible to ensure best performance. Lack of processing power on the Agent Manager manifests in missed collections and gaps in the data usually noticeable in various graphs throughout the Foglight for VMware dashboards.

Foglight Management Server minimum memory requirements

# of virtual machines Memory*
Foglight JVM settings


2500 Xms|Xmx=9G
5000 Xms|Xmx=17G
10000 Xms|Xmx=32G
20000 Xms|Xmx=62G

* Edit the Foglight Management Server JVM settings in the server.config file located under Quest\Foglight\config\. When running Foglight on a virtual machine, full memory needs be reserved at the hypervisor level.


Product licensing

Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.

Foglight for VMware is covered by the base Foglight Evolve license and Foglight for Virtualization, Enterprise Edition license. A separate additional license is required for installation in the base Foglight product.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.



Getting started with Foglight for VMware

Getting started with Foglight for VMware

Contents of the release package

Foglight for VMware release package contains the following:

  1. Cartridge files:
    Note: Some of the Foglight for VMware browser interface elements are defined in the,, and All of the available CAR files need to be installed on the Management Server.
  2. Product Documentation, including:
    • Foglight for VMware Release Notes (this document, in HTML format)
    • Foglight for VMware Installation Guide (PDF)
      Note: This document was not updated for this release. The previous version of this document is relevant for the current release as well.
    • Foglight for VMware User and Reference Guide (PDF and online help)
      This document was not updated for this release. The previous version of this document is relevant for the current release as well.

Installation instructions

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 is installed with Foglight Evolve 9.2 or Foglight for Virtualization, Enterprise Edition 8.9.2.

Important: To enable the VMware Performance Agent to monitor your virtual environment, you must grant the agent privileges for accessing the Virtual Center and collecting data from it, as described in "Granting the VMware Performance Agent Privileges to Collect Data from a Virtual Center" in the Foglight for VMware Installation Guide. However, when you create an administrative role in the Virtual Center for that purpose, in addition to the Datastore > Browse Datastores and Sessions > View and Terminate Sessions privileges, that role must also include 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. Also, any existing Virtual Center accounts that the VMware Performance Agent already uses to log in to the monitored Virtual Center must be granted the Performance > Modify intervals privilege.

To install the cartridge files and deploy VMware Performance agents:
  1. Navigate to the Cartridge Inventory dashboard, and install the following cartridge files in this order:
  2. On the Agent Status dashboard, click Deploy Agent Package to deploy the VMware-Performance-64bit-AgentInstaller package to desired hosts.
  3. On the VMware Environment dashboard, on the Administration tab, create VMware Performance agent instances, and edit their properties, as required.
  4. Activate the newly created VMware Performance agent instances, and start their data collection.

After installing all of the cartridge files, the following cartridges appear on the list of installed cartridges:

  • Virtual-VMware 5.8.2
  • Virtual-VMware-Admin 5.8.2
  • Virtual-VMware-Base 5.8.2
  • Virtual-VMware-Lite 5.8.2
  • Virtual-VMware-Dependencies 5.8.2
  • Virtual-VMware-Intelliprofile 5.8.2
  • VMware-Performance-Agent 5.8.2

For more information, see the Foglight for VMware Installation Guide.

Additional resources

Additional information is available from the following:


This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: This release is localized for English only but supports the Unicode character set.


About Us

About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request.
  • View Knowledge Base articles.
  • Sign up for product notifications.
  • Download software and technical documentation.
  • View how-to-videos.
  • Engage in community discussions.
  • Chat with support engineers online.
  • View services to assist you with your product.


Copyright© 2020 Quest Software Inc.

Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating