View Source

Managing Sync / vSync

To take full advantage of integrated virtual and physical monitoring, it is important to understand how to manage virtual machine inventories in Uptime Infrastructure Monitor, and how Sync (Hyper-V) and vSync (VMware vCenter) keep Uptime Infrastructure Monitor abreast of them.

When a Hyper-V host or VMware vCenter server is added as an Element to Uptime Infrastructure Monitor, all component ESX servers and (by default) VMs are also added as Elements. It is at the Hyper-V host and 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 host 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 Sync/vSync maintains an accurate mirror. See Virtual System Configuration Mirroring for more information.

Managing Virtual System Inventories in Uptime Infrastructure Monitor

After a Hyper-V host or 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. The same is true for a Hyper-V host server's guest VMs. As a central monitoring configuration point, the host Element gives you the ability to determine which VMs are monitored in Uptime Infrastructure Monitor and as a consequence, which Hyper-V or VMware vSphere metrics are kept in the DataStore.

You can select VMs or a Hyper-V or ESX host to be "ignored" by Uptime Infrastructure Monitor. When VMs are ignored, their topological relationship to other virtual system 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 Hyper-V host and ESX servers in your virtual infrastructure, other factors may dictate your monitoring policies:

because the VMs on your Hyper-V or ESX servers count toward your Uptime Infrastructure Monitor license, you may have resource monitoring restrictions that require prioritization
you are not interested in keeping performance metrics for some parts of your virtual infrastructure (e.g., some VMs are used for testing, and are not considered mission-critical)
similarly, as ignored VMs do not appear in live monitoring pages in Uptime Infrastructure Monitor such as Global Scan or the Resource Scan dashboards, you may want to exclude non-essential VMs to avoid cluttering the views

On the Hyper-V host or 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 Hyper-V or 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:

if there is enough license space for the Hyper-V or ESX host and all of its VMs, they are monitored
if there is no more license space, the host and all of its VMs are added (with its hierarchy intact) to the list of ignored Elements
if there is license space for some of the Elements, the hosts are added and monitored, and each child VM is added to the monitored list until license space has run out; the remaining VMs are added to the list of ignored Elements

Once these 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.

Viewing vCenter Inventory Summaries

To see an overview of your VMware vCenter Element’s inventory, do the following:

In the Infrastructure panel, click the gear icon beside the VMware vCenter server, then in the pop-menu, select View.
On the VMware vCenter Element profile page, ensure the Info tab is selected.
Click Inventory Summary.

On this page, you can see your VMware vCenter server’s total available resource counts, further broken down by datacenter.

Removing Elements from Monitored Inventories

To stop Uptime Infrastructure Monitor from monitoring virtual server Elements, do the following:

In the Infrastructure panel, click the gear icon beside the Hyper-V host or VMware vCenter server, then in the pop-menu, select View.
On the Element profile page, ensure the Info tab is selected.
Click Inventory for Hyper-V or Inventory Detail for vCenter.
In the Inventory Detail page, select the checkboxes that correspond to the ESX hosts or clusters (if applicable), or individual VMs that you want to stop monitoring.
Click Add Selected Elements to Ignore.

The inventory page refreshes, with your selections appearing in the Ignored Elements section.

Re-adding Ignored Elements to Monitored Inventories

To resume monitoring virtual server Elements in Uptime Infrastructure Monitor, do the following:

In the Infrastructure panel, click the gear icon beside the Hyper-V host or VMware vCenter server, then in the pop-menu, select View.
On the Element profile page, ensure the Info tab is selected.
Click Inventory for Hyper-V or Inventory Detail for vCenter.
On the Inventory Detail page, from the Ignored Elements list, select the checkboxes that correspond to the ESX hosts or clusters (if applicable), or 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.

Sync/vSync Settings

From the Hyper-V host or 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 topology. This means you can bundle virtual server 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 Virtual System Configuration Mirroring for more information on the types of virtual system events that Uptime Infrastructure Monitor watches for.

vSync Configuration Settings (vCenter)

The following settings are used to configure a VMware vCenter server’s vSync behavior:

Alert Profiles	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.
Action Profiles	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.

Sync Configuration Settings (Hyper-V)

The following settings are used to configure a Hyper-V server’s Sync behavior:

Automatically remove deleted elements

A switch that allows you to set Sync to automatically remove deleted elements form inventory upon discovery.

Collect Virtual Machine data

A switch that allows you to control the discovery and monitoring of virtual machines and their performance data.

Switching this option frequently is not recommended as changes will take some time to complete and result in mass creation/deletion of VMs.

Alert Profiles

A list of alert profiles (listed in alphabetical order) that are triggered when new virtual machines belonging to the VM server are discovered when Sync scans the Hyper-V topology.

Action Profiles

A list of action profiles (listed in alphabetical order) that are triggered when new VMs belonging to the VM server are discovered when Sync scans the Hyper-V topology.

Changing Sync/vSync Settings

To modify how Sync/vSync mirrors a Hyper-V host or VMware vCenter server Element’s configuration in Uptime Infrastructure Monitor, do the following:

In the Infrastructure panel, click the gear icon beside the Hyper-V host or VMware vCenter server, then in the pop-menu, select View.
On the Element profile page, ensure the Info tab is selected.
In the Sync or vSync section, click Edit Settings.

Make changes to Sync/vSync settings as needed:

modify the alert profile or action profile lists for newly discovered VMs in the specified Infrastructure group
modify the alert profile or action profile lists for newly discovered Hyper-V host or ESX servers in the specified Infrastructure group

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.

Click Save.

Manually Resyncing Uptime Infrastructure Monitor with a Hyper-V or vCenter Topology

To force Uptime Infrastructure Monitor to resync with a Hyper-V or 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:

In the Infrastructure panel, click the gear icon beside the Hyper-V host or VMware vCenter server, then in the pop-menu, select View.
On the Element profile page, ensure the Info tab is selected.
In the Sync or vSync section, click Resync Now.

A Resyncing status update persists until Uptime Infrastructure Monitor has completed the Sync/vSync process. Once the sync operation is complete, the polling intervals configured for the server is reset.