サポートと今すぐチャット
サポートとのチャット

Foglight for VMware 5.7.7 - User and Reference Guide

Using VMware Monitoring in Foglight for Storage Management Reference Appendix: Alarm Messages Appendix: Metrics

Generating reports

Generating reports

VMware Monitoring in Foglight for Storage Management includes a report generation ability. This allows you to create reports using a set of predefined templates to report on the various aspects of your virtual environment. VMware Monitoring in Foglight for Storage Management includes a collection of predefined report templates.

You can generate, copy, and edit reports using the Reports dashboard included with the Management Server.

Available report templates

The following templates are available with VMware Monitoring in Foglight for Storage Management.

 
Table 4. VMware Monitoring in Foglight for Storage Management report templates
Report Template Name
Object Type
This template can be used to generate a report that…
Datastore Reclamation and Addition

Service

Shows the capacity of the selected datastores and lists the ESX hosts and virtual machines that are connected to them. Information about the logical and physical disks on the virtual machines is also displayed in this report.

Storage Reclamation And Addition By ESX Hosts

Datastore

Shows the datastore usage per ESX host.

Storage Reclamation And Addition by Virtual Machines

Service

Shows the capacity and usage of logical and physical disks on the selected virtual machines.

Virtual Machines Disk Space Addition - Detail

Service

Shows relevant details for all virtual machines with a given percentage (or less) free storage available.

Virtual Machines Disk Space Addition - Summary

Service

Summarizes relevant details for all virtual machines with a given percentage (or less) free storage available.

Virtual Machines Disk Space Reclamation - Detail

Service

Shows relevant details for all virtual machines with a given percentage (or less) free storage available.

Virtual Machines Disk Space Reclamation - Summary

Service

Summarizes relevant details for all virtual machines with a given percentage (or less) free storage available.

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 for Virtualization, Enterprise Edition 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.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択