Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for VMware 6.1.0 - User Guide (Lite version)

Using Foglight for VMware Reference Appendix: Alarm Messages Appendix: Metrics

VMware Performance Agent configuration

The VMware Performance Agent collects data from the virtual infrastructure and sends it to the <Product Name>™ Management Server. The agent keeps track of resource utilization metrics and alerts you when certain pre-defined thresholds are reached.

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 to 500 virtual machines. If the total number of virtual machines to be monitored from a single agent host is greater than 500, 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.

 
Table 5. Foglight VMware Performance Agent host system requirements
 
Minimum CPU
Minimum Memory
Total Monitored VMs
Windows 64-bit

21

4 GB

2000

Linux 64-bit

21

4 GB

2000

1 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 2560 MB of memory:

512 MB + 2048 MB = 2560 MB

This is the default setting for agents deployed on 64-bit systems.

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

512 MB + 4096 MB = 4608 MB

This requires a change in the default Agent Manager settings.

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 MB – 2560 MB = 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 to the memory settings section:
vmparameter.0 = "-Xms2048m";
vmparameter.1 = "-Xmx2048m";
 
* 
NOTE: If this file has been previously edited have been made to this file, increment the numeric parameters accordingly.
4
Delete the existing deployed negotiation configuration settings directory:
<Agent_Manager_home>/state/default/config/deployments
5
Restart the Agent Manager for these settings to take effect.

Host system recommendations

Dedication

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.

Memory

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

Or:

2048 + 4608 MB = 6656 MB

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

CPU

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.

 
Table 6. CPU usage guidelines
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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation