Chat now with support
Chat with Support

Foglight for VMware 5.8.1 - 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

Planning for virtual machine migrations

Additional features

The VMware Modeler dashboard provides a mechanism you can use to view the impact that migrating a virtual machine will have on a target ESX Host. This dashboard takes up the entire display area of the Foglight for VMware browser interface. It can be accessed in two different ways:

•
If you are in the VMware Explorer dashboard, you can access the VMware Modeler dashboard by using the Run Migration Modeler link under the Actions heading on the action panel to the right of the Foglight for VMware browser interface. For more information about the action panel with respect to Foglight for VMware tasks and actions, refer to Accessing VMware actions and tasks .
•
From within any dashboard, you can access the VMware Modeler dashboard by clicking the VMware Modeler link under Dashboards > Virtual > VMware in the navigation panel.
Figure 53. Migration Modeler

The VMware Modeler dashboard provides four graphs that show current and projected numbers, for CPU and memory utilization and network and disk activity, on the target ESX Host over the time range specified in the VMware Explorer dashboard.

The blue area on the graphs represents current consumption or activity on the target ESX Host. The orange area specifies projected worst case consumption or activity. The red dotted line specifies the target ESX Host capacity with respect to the corresponding metric. For reference information about the data appearing on this dashboard, see VMware Modeler views .

To run the Migration Modeler:
1
From the VirtualCenter list, select the vCenter within which the migration will take place.
2
From the Virtual Machine list, select the virtual machine that is to be migrated.
3
From the Target Host list, select the ESX Host that will be the target for the migration.

When using the VMware Modeler dashboard, you should extend the time range in order to better assess the long term impact of the potential migration. For specific information about adjusting dashboard time ranges, refer to the Foglight for VMware User Guide.

Creating OS mapping rules

Creating OS mapping rules

OS mapping involves associating various versions and editions of a particular operating system with a common OS name. You configure OS mapping rules using the Administration tab on the VMware Environment dashboard. This helps Foglight for VMware map the OS names reported by Foglight for VMware to those reported by physical OS monitoring, so that you can view all Windows machines, all Linux machines, and so on.

For reference information about this view, see OS Mapping view .

To configure OS mapping rules:
•
On the VMware Environment dashboard, open the Administration tab and click Configure OS Mapping.
The OS Mapping view appears.
To add an OS mapping rule:
1
In the OS Mapping view, click Add.
The Add OS Mapping Rule dialog box appears.
2
In the Add OS Mapping Rule dialog box, in the Matching Text box, type the OS name with its edition and/or version number to help Foglight for VMware identify the operating system.
3
In the Common OS Name list, select the shorter common OS name.
4
Click Save.
Foglight for VMware matches the shorter common OS name with the text you provided in Step 2.
To delete an OS mapping rule:
1
In the OS Mapping view, select an OS mapping rule by clicking the associated check box in the left column.
2
Click Delete.
3
Click Save.
To configure the priority of an OS mapping rule:
•
In the OS Mapping view, move a rule one level up by clicking the up arrow in the rule’s row.
•
Move a rule one level down by clicking the down arrow in the rule’s row.

Reviewing object instances and limits

Reviewing object instances and limits

Foglight collects data from monitored environments and creates a data model in real-time. The resulting topology model consists of nodes where each node is an object instance of a particular object type. Each type of monitoring environment can have a unique set of object types. Foglight for VMware includes a set of topology object types and their definitions. When Foglight collects data from your VMware environment, it builds the topology model that consists of the instances of the object types defined by Foglight for VMware. By default, a monitored environment can result in up to 50,000 object instances being created by a single object type. This value is controlled by the foglight.limit.instances registry variable.

Registry variables have a global default value and type-specific scoped values. This means that different object types can have different instance limits.

Explore the Instances and Limits view to see the existing VMware object types. To access this view, on the VMware Environment dashboard, open the Administration tab, and click Review Instances and Limits.

Figure 54. Instances and Limits

The Instances and Limits view displays the list of the existing VMware object types, and for each type it shows the type name, instance limit, instance count, instance limit utilization, and the current status given as a highest severity level associated with an instance of that type. This information can give you insight into the size of your database and whether additional adjustments are required to improve your system performance. For example, if an object type results in a high number of object instances, this may result in performance bottlenecks. To prevent them, check if any of these are updated recently and, if not, delete them from the database.

To view the list of existing registry variables or to edit them, click Edit Registry Variable in the top-left corner. For complete information about registry variables, see the Administration and Configuration Help.

For reference information about this view, see Instances and Limits view .

Configure Metrics Collection

VMware agent has collect total 99 metrics from vCenter, but some metrics are not used to VMware dashboard and relate products (Capacity Director, Optimizer and so on), so the user can disable the collection of these metrics at this view.

For reference information about this view, see Metrics Collection Management View .

To configure the metrics collection:

1
On the navigation panel, under Dashboards, choose VMware > VMware Environment.
2
On the VMware Environment dashboard that appears in the display area, choose Administration > Advanced Options, click Metrics Collection Management.
3
Select the agent, click the button Collect Metrics For Dashboard Only or Restore The Default Setting, and then click the button Save Edited Configuration. The default setting is collect all metrics.
* 
NOTE: User can also select/deselect the Collecting checkbox, but we wouldn’t recommend it because some metrics have been used for conversion of other metrics.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating