Chat now with support
Chat mit Support

Foglight for VMware 5.8.2 - User and Reference 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

Setting the vSwitchCollector properties

A vSwitch collector is a component that captures metrics from virtual switches on the monitoring system. The vSwitchCollector properties instruct the VMware Performance Agent which virtual switches to monitor.

1
Locate the VMware Performance Agent’s vSwitchCollector properties.
2
Set the vSwitchCollector properties as follows:
Monitoring Switches: Select a list in which you want to specify the VMware virtual switches that you want to monitor. You can select or clone an existing list, and edit it, as required. The default list is monitoredSwitchList. Lists can be shared between multiple agent instances. For more information about list properties, see the Administration and Configuration Help.
DVS Managed Object Reference: The managed object reference of the distributed virtual switch.
Other Switches (Non-VMware): Select a list in which you want to specify the non-VMware virtual switches that you want to monitor. You can select or clone an existing list, and edit it, as required. The default list is monitoredSwitchList. Lists can be shared between multiple agent instances. For more information about list properties, see the Administration and Configuration Help.
DVS Managed Object Reference: The managed object reference of the distributed virtual switch.
3
Click Save.

Setting the Duplicate VM List properties

A duplicated virtual machine is a copy or clone of an existing VM in your environment. The Duplicate VM List properties indicate to the VMware Performance Agent which virtual machines are duplicates or clones of the existing VMs.

1
Locate the VMware Performance Agent’s Duplicate VM List properties.
2
Set the Duplicate VM List properties as follows:
Duplicate VM List MOR: Select a list in which you want to specify the duplicated virtual machines. You can select or clone an existing list, and edit it, as required. The default list is duplicateVMListList. 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 Duplicate VM Item property to contain the managed
3
Click Save.

Setting the Black List properties

In some rare cases, the VMware Performance Agent can encounter ESX® hosts and virtual machines for which it cannot collect data. To prevent these problems, the VMware Performance Agent detects these entities, excludes them from data collection, and adds them to the agent black list.

Any metrics associated with these objects are not included in roll up performance metrics. When an entity is added to the agent black list, an agent message and alarm are generated makes you aware of the problem so that you can investigate it further in the monitored VMware® environment. When the issue with the entity is resolved, it can be removed from the agent black list. The next available performance collection includes this entity in the data collection request.

In addition to the list that is populated by the agent, there is a user-populated black list. You populate this list by adding ESX hosts and virtual machines that you want to exclude from data collection. This feature enables Foglight administrators to disable data collection for certain ESX hosts and virtual machines, which also prevents their performance metrics from being submitted to Foglight.

Any metrics associated with these objects are submitted as part of roll up metrics. For example, if a virtual machine that appears on the user-populated black list is part of a resource pool, the virtual machine performance metrics are included with the performance metrics of other virtual machines from the same resource pool. This resource pool performance data is collected and submitted to Foglight. At the same time, the black-listed virtual machine object will not appear to have any performance metrics stored for this object. ESX hosts are handled the same way in terms of rolling up performance data for clusters, datacenters, or the Virtual Center.

Each ESX host or virtual machine entry in the user black list should include the Managed Object Reference (MOR) value. The MOR value is assigned to monitored objects in the monitored VMware environment and is collected by Foglight for VMware. This value is stored in the Managed Object Reference property of ESX host and virtual machine objects. You can use the Data Browser to find out the MOR values for those ESX hosts or virtual machines that you want to exclude from data collection.

The agent checks both lists during data collection. You can remove entities from either list, as required. For example, if you resolve an issue with a virtual machine that causes data collection problems, you can remove the virtual machine from the black list.

For any ESX hosts or virtual machines that you want to exclude from data collection an entry should exist in the agent or user black lists. While you can add entries to the user lists, agent black lists should only be populated by the VMware Performance Agent. Any ESX hosts or virtual machines for which you want to enable data collection must have their entries removed from either black lists.

Every VMware Performance Agent instance is associated with an agent and a user black list. Each agent instance should maintain a unique pair of these lists. Because list properties in Foglight (also known as secondary properties) are shareable properties, meaning that they are accessible to all agent instances of the type in which they are defined, you should clone an agent and a user black list for each agent instance and give them unique names.

Entities included in these lists are not included in the collection of performance metrics. Other collections are not affected by their contents.

a
Choose the user black list that you want to use for this agent instance. Click the User BlackListed MORs list, and select the black list. The default list is userBlackList.
The Clone userBlackList dialog box appears.
c
In the Clone userBlackList dialog box, type the name of the user black list. It is recommended to use a syntax that makes the list name unique and easily associated with this agent instance. For example: <list_name>_<agent_name>
d
Click OK to close the Clone userBlackList dialog box.
a
Click Edit on the right of the User BlackListed MORs list.
The VMwarePerformance - userBlackList dialog box appears.
To black list an ESX host or virtual machine, click Add Row, and in the new row that appears, in the BlackList Item column, specify the ESX host or virtual machine using the following syntax:
<host|vm>-<MOR>
host: Indicates that the black list item is an ESX host.
vm: Indicates that the black list item is a virtual machine.
MOR: The value of the Managed Object Reference property of the ESX host or virtual machine that you want to exclude from data collection.
4
Click Save.

Setting the Data Collection Scheduler properties

Use the Data Collection Scheduler properties to adjust how frequently the VMware Performance Agent collects data from the monitored server.

1
Locate the VMware Performance Agent’s Data Collection Scheduler properties.
2
Set the Data Collection Scheduler properties as follows:
Collector Name: The name of the collector. A collector is a component that captures specific type of metrics. Existing collectors are: Relationship And Hierarchy Data, Inventory Entity Properties, Performance Metrics, and Events Collection.
Default Collection Interval: Contains the length of the default collection interval. The default collection intervals for the existing collectors are:
Time Unit: Contains the time unit for measuring the default collection interval: milliseconds, seconds, minutes, hours, or days.
Fast-Mode Collection Interval: Contains the length of the collection interval when the agent is running in fast mode.
Fast-Mode Time Unit: Contains the length of the collection interval when the agent is running in fast mode.
Fast-Mode Max Count: Contains the maximum count of entries when the agent is running in fast mode.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen