Foglight for VMware 5.7.7 - User and Reference Guide

Additional features

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 VMware Monitoring in Foglight for Storage Management map the OS names reported by VMware Monitoring in Foglight for Storage Management 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 .

Creating OS mapping rules

Additional features

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 VMware Monitoring in Foglight for Storage Management map the OS names reported by VMware Monitoring in Foglight for Storage Management 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 .

Reviewing object instances and limits

Foglight for Storage Management 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. VMware Monitoring in Foglight for Storage Management includes a set of topology object types and their definitions. When Foglight for Storage Management collects data from your VMware environment, it builds the topology model that consists of the instances of the object types defined by VMware Monitoring in Foglight for Storage Management. 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 Agent Administration dashboard, click Review 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:

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.