立即与支持人员聊天
与支持团队交流

Foglight for VMware 7.1.0 - User Guide

Using Foglight for VMware
Introducing the virtual infrastructure Navigation basics Interacting with Foglight for VMware VMware Performance Agent configuration
Reference
Views
VMware Alarms views VMware Explorer views VMware Modeler views VMware VirtualCenter views VMware Environment views Other views
Rules
Agent Rules Cluster Rules Datacenter Rules Datastore Rules Resource Pool Rules ESX Server Rules VirtualCenter Rules Virtual Machine Rules VMW Stale Data Management Rule Virtual Switch Rules
Appendix: Alarm Messages Appendix: Metrics

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.

Configuring agent properties

When an agent connects to <Product Name>™, it is provided with sets of properties that it uses to configure its correct running state. Each agent is provided with a combination of two types of properties: agent properties and shareable properties.

Default versions of these properties are installed with Foglight for VMware. However, you can edit the default shareable and agent properties, configure agent properties that apply only to a specific agent instance, and create edited clones of shareable properties that are used by a subset of agents of a certain type.

There are two ways to access the VMware Performance Agent properties:

•
On the VMware Environment dashboard, on the Administration tab, select an agent instance and click Edit Properties (see Configuring monitoring agents for data collection ). This method only provides access to the Configuration properties, but not the Black List and Data Collection Scheduler properties.
•
On the Agent Status dashboard, select an agent instance and click Edit Properties. This method provides access to the full set of VMware Performance Agent properties, and is described in this topic.

For more information about working with agent properties, see the Administration and Configuration Guide.

To modify agent properties:
1
Log in to the Foglight browser interface.
2
Ensure that the navigation panel is open.
To open the navigation panel, click the right-facing arrow on the left.
3
Navigate to the VMware Performance Agent properties. An agent instance can have a combination of global and private properties. Global properties apply to all instances of the agent type, while private properties apply only to specific agent instances.
a
On the navigation panel, under Dashboards, choose Administration > Agents > Agent Status.
 
* 
IMPORTANT: Another way of editing the VMware Performance Agent properties is through the Agent Properties dashboard. The properties you specify on this dashboard apply to all instances of the VMware Performance Agent type. To be certain that you are editing properties for a particular agent instance, without overwriting any properties of other VMware Performance instances, use the Agent Status dashboard instead of the Agent Properties dashboard.
b
On the Agent Status dashboard, select the instance of the VMware Performance Agent whose properties you want to modify and click Edit > Edit Properties.
c
Click Modify the private properties for this agent to indicate that you want to edit the properties of the selected VMware Performance Agent instance.
A list of agent properties appears in the display area.

The configuration of agent properties described in this section include:

•
Setting the Configuration properties
•
Setting the FileCollector properties
•
Setting the vSwitchCollector properties
•
Setting the Duplicate VM List properties
•
Setting the Black List properties
•
Setting the Data Collection Scheduler properties

Setting the Configuration properties

The Configuration properties point the VMware Performance Agent to the machine on which the Virtual Center is running, and provide some additional configuration settings.

To set the Configuration properties:
1
Locate the VMware Performance Agent’s Configuration properties.
2
Set the Configuration properties as follows:
•
Host Name: The fully qualified host name of the machine on which the Virtual Center is running.
•
Host Port: The port number of the machine on which the Virtual Center is running that will be used by the VMware Performance Agent to connect to that machine in order to collect data from the monitored Virtual Center.
•
Performance request threads: The number of threads in a performance request.
•
Cisco switch collection threads: The number of threads in a Cisco switch collection.
•
Storage Collection Enabled: If you are running <Product Name>™ for Storage Management and want to enable the VMware Performance Agent to collect the Foglight Storage data, select True, otherwise, set this property to False. Foglight for Storage Management can help you optimize the VMware environment virtual storage and its underlying physical storage components. For more information about this product, see your Foglight for Storage Management documentation.
•
VMWare Request Timeout (sec): The amount of time in seconds after which a VMware request times out.
•
Default performance request timeout (sec). Increased as needed: The amount of time in seconds after which a default performance request times out.
•
Property request timeout (sec): The amount of time in seconds after which a property request times out.
•
Update request timeout (sec): The amount of time in seconds after which an update request times out.
•
Login/open/close timeout (sec): The amount of time in seconds after which login, open, or close requests times out.
•
Cisco switch connection timeout (sec): The amount of time in seconds after which a Cisco switch connection times out.
•
Cisco switch timeout (sec) for performing a single SSH command: The amount of time in seconds after which an attempt to perform a single SSH command on a Cisco switch times out.
•
Request Timeout for HA operation (sec): The amount of time in seconds after which an HA operation request times out.
•
Request Timeout for move vm operation (min): The amount of time in minutes after which a request for an operation to move a virtual machine times out.
•
Alarms Collection Enabled: If you want to collect VMware alarms from the monitored system, set this to True. Otherwise, select False.
•
Performance request batch size (10-50): The size of a performance request batch.
•
Performance submission batch size: The size of a performance submission batch.
3
Click Save.

Setting the FileCollector properties

A file collector is a component that captures metrics from specific files on the monitoring system. The FileCollector properties instruct the VMware Performance Agent which datastores, file directories, and files to exclude from monitoring.

To set the FileCollector properties:
1
Locate the VMware Performance Agent’s FileCollector properties.
2
Set the FileCollector properties as follows:
•
Excluded Datastores: Select a list in which you want to specify the datastores that you want to exclude from monitoring. You can select or clone an existing list, and edit it, as required. The default list is excludedDatastoresList. Lists can be shared between multiple agent instances. For more information about list properties, see the Administration and Configuration Help.
For each datastore entry in the list, set its properties as follows:
•
Datastore Name: The name of one or more datastores that you want to exclude from monitoring. To specify multiple datastores, you must use regular expressions.
•
Regex Flag: Indicates if the Datastore Name contains a regular expressions.
•
Excluded Folders: Select a list in which you want to specify the file directories that you want to exclude from monitoring. You can select or clone an existing list, and edit it, as required. The default list is hiddenFolders. Lists can be shared between multiple agent instances. For more information about list properties, see the Administration and Configuration Help.
For each directory entry in the list, set its properties as follows:
•
Folder Name: The path to one or more directories that you want to exclude from monitoring. To specify multiple directories, you must use regular expressions.
•
Regex Flag: Indicates if the Folder Name contains a regular expressions.
•
Excluded Files: Select a list in which you want to specify the files that you want to exclude from monitoring. You can select or clone an existing list, and edit it, as required. The default list is vmwareSrmFiles. Lists can be shared between multiple agent instances. For more information about list properties, see the Administration and Configuration Help.
For each directory entry in the list, set its File Name Regex property to a regular expression that points to one or more files that you want to exclude from monitoring.
3
Click Save.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级