...
vSphere Components as up.time Elements
Some VMware vSphere components that act as logical groupings, including datacenters, clusters, resource pools, and vApps, are hierarchically mirrored in up.time’s My Infrastructure inventory, and are represented through their reported resource metrics. On the other hand, VMware vSphere components that are actual hosts, whether virtual or physical (i.e., a VMware vCenter server, its component ESX servers,or their respective VMs) are represented in up.time as Elements.
When you add a VMware vCenter server as an Element, all of the VMware vSphere components, whether organizational or compute resources, as defined through the vSphere Client, are imported to up.time, and their VMware/vSphere-collected metric data is migrated to the up.time DataStore. Additionally, all ESX servers and VMs also become Elements.
There will be cases where administrators will want to actively manage which ESX server Elements (and subsequently, which VMs) are monitored by up.time. For example, licensing constraints may prevent you from monitoring every ESX server in up.time, or the performance of particular portions of your virtual infrastructure may not be considered mission critical, and demand the same level of uptime.
In these cases, administrators can include or exclude specific up.time Elements from being monitoredmonitoring. Exclusions can be made on a per-VM basis, or by a logical grouping at the VMware vSphere level (e.g., by cluster).
Any VMware vCenter component is by default represented in My Infrastructure as either a known host or a known VM, and is grouped as such in the inventory. (By default, the My Inventory group names are Discovered Hosts and Discovered VM Hosts ). When Elements are ignored, they are removed from My Infrastructure. If new hosts or VMs are discovered during vSync, they are added to the appropriate My Infrastructure group.
For more information, see Managing vCenter Inventories in up.time.
...