To take full advantage of integrated virtual and physical monitoring, it is important to understand how to manage VMware vSphere inventories in Uptime Infrastructure Monitor, and how vSync keeps Uptime Infrastructure Monitor abreast of them.
When a VMware vCenter server is added as an Element to Uptime Infrastructure Monitor, its component ESX servers and (by default) VMs are also added as Elements. It is at the vCenter-Element level that you can tweak what is monitored. Additionally, you can “promote” VM Elements to be monitored with greater depth using the Uptime Infrastructure Monitor Agent or WMI.
The dynamic nature of a VMware vCenter server’s configuration is easily managed by Uptime Infrastructure Monitor through automated profile monitoring; whatever you have included in your inventory as parent-level items, Uptime Infrastructure Monitor vSync maintains an accurate mirror. See vCenter Configuration Mirroring for more information.
After a VMware vCenter server is added as an Element to Uptime Infrastructure Monitor, you can manually manage all of its inventory. By default, all of a VMware vCenter’s components—ESX hosts and clusters, and their child VMs—are monitored by Uptime Infrastructure Monitor. As a central monitoring configuration point, the VMware vCenter Element gives you the ability to determine which VMs are monitored in Uptime Infrastructure Monitor and as a consequence, which VMware vSphere metrics are kept in the DataStore.
You can select VMs or an ESX host to be "ignored" by Uptime Infrastructure Monitor. When VMs are ignored, their topological relationship to other VMware vCenter components is retained, but their metrics are no longer recorded to the DataStore, and they no longer count toward your license.
As the topology of your virtual infrastructure changes, you can change the contents of the ignore list. Historical data for VM Elements are retained in the DataStore, regardless if they are currently monitored or ignored, allowing administrators to continue to perform diagnosis on a continuously changing virtual environment.
If graphs or reports are generated that include time or date ranges where no data were collected for a VM Element, those ranges in the charts show no data.
Although there are no resource-related reasons why you would not want Uptime Infrastructure Monitor to monitor all ESX servers in your virtual infrastructure, other factors may dictate your monitoring policies:
On the VMware vCenter Element’s Info page, you can view its complete inventory, broken down by logical groupings created in the vSphere Client (e.g., by datacenter). It is here you can add or remove ESX hosts or VMs (as individual machines, or in groups at the datacenter or cluster level) from the ignore list.
For license management, ignoring or monitoring a parent object correspondingly frees up or uses license spots for all of its child objects, provided there is space. For example, if the VMware vCenter Element is configured to Collect Virtual Machine data, adding an ESX host automatically includes its VMs, each of which counts toward your license. Consider the following outcomes:
Once VMware vCenter objects are added, you can manage license usage by moving Elements from monitored inventories to lists of ignored Elements, or vice versa.
If you configured the VMware vCenter server to not collect and report on VM data, and only work with ESX hosts and clusters, inventory management is done only at that inventory level.
To see an overview of your VMware vCenter Element’s inventory, do the following:
On this page, you can see your VMware vCenter server’s total available resource counts, further broken down by datacenter.
To stop Uptime Infrastructure Monitor from monitoring VMware vCenter server Elements, do the following:
The inventory page refreshes, with your selections appearing in the Ignored Elements section.
To resume monitoring VMware vCenter server Elements in Uptime Infrastructure Monitor, do the following:
On the vCenter Inventory Detail page, from the Ignored Elements list, select the checkboxes that correspond to the ESX hosts or clusters, or (if applicable) individual VMs that you want to start monitoring.
To streamline the process, you can only select or remove VMs or datacenters as they were added. For example, if you added an entire datacenter to the ignore list, you cannot select individual VMs.
Click Remove Selected Elements from Ignore List.
The inventory page refreshes, with your selections appearing in the active monitoring section.
From the VMware vCenter server Element’s Info page, you can configure how Uptime Infrastructure Monitor polls the server’s topology for changes, and what Uptime Infrastructure Monitor does when changes are encountered.
Using alert and action profiles, you can configure an extensive set of behaviors depending on what changes occur with the VMware vCenter topology. This means you can bundle VMware vSphere events with the those you normally track in your physical infrastructure.
For example, if your VMware vSphere environment is configured to dynamically allocate more compute resources to a specific department at a specific time of year (e.g., the end of the fiscal year for the accounting department), you can use Uptime Infrastructure Monitor to detect CPU changes to the appropriate resource pool, and confirm this action in a log.
See vCenter Configuration Mirroring for more information on the types of VMware vSphere events that Uptime Infrastructure Monitor watches for.
The following settings are used to configure a VMware vCenter server’s vSync behavior:
A list of alert profiles (listed in alphabetical order) that are triggered when new VMs or ESX hosts belonging to the VMware vCenter server are discovered when vSync scans the VMware topology.
A list of action profiles (listed in alphabetical order) that are triggered when new VMs or ESX hosts belonging to the VMware vCenter server are discovered when vSync scans the VMware topology.
Default Basic Performance Data Polling Interval
The amount of time, in minutes, that Uptime Infrastructure Monitor waits between metric data retrieval operations for newly discovered ESX servers.
Select the Apply to Existing ESX Servers check box to have this modified polling interval applied to all ESX servers that are part of the VMware vCenter server’s topology, and the Uptime Infrastructure Monitor inventory. Any ESX server whose polling rates are individually changed conforms to this new global setting.
Default Advanced Performance Data Polling Interval
The advanced data settings perform the same functions as those above, but are for advanced VMware vSphere metrics.
To modify how vSync mirrors a VMware vCenter server Element’s configuration in Uptime Infrastructure Monitor, do the following:
modify the ESX server polling intervals, and indicate whether this change is to be retroactively applied to all known ESX servers
The polling intervals modified here apply only to newly-discovered ESX servers via vSync. Whether individually configured, or from a previous global setting, existing ESX server Elements in Uptime Infrastructure Monitor use older intervals, unless you use the Apply to Existing ESX Servers option.
To force Uptime Infrastructure Monitor to resync with a VMware vCenter server (i.e., search for new VMs and ESX servers, metric data for monitored Elements, and changes to the topology), do the following:
A Resyncing status update persists until Uptime Infrastructure Monitor has completed the vSync process. Once the sync operation is complete, the polling intervals configured for this VMware vCenter server is reset.