Hypervisor Monitoring Requirements
  • Dark
  • PDF

Hypervisor Monitoring Requirements

  • Dark
  • PDF

Supported Hypervisor Platforms

ControlUp supports VMware v4.x/5.x/6.x/7.x environments that are managed by vCenter. Standalone ESX/ESXi servers are not supported. ControlUp also supports Citrix XenServer v6.1 (with the Performance Monitoring Enhancement Pack, CTX135033), v6.2, v7.0 and v8.x. For earlier versions, some performance columns might not yet bebimplemented in XenServer and may be displayed as N/A.

Microsoft Hyper-V 2012 R2, Microsoft Hyper-V 2016, including standalone and clustered hosts. Note that you need to install the ControlUp Agent on the Hyper-V hosts to enable monitoring them as hypervisors. The console does not work on any version of Core, but the agent is fine as long as you have .NET Framework 4.5 or higher installed,

The ControlUp Console supports two hypervisor platforms running on Nutanix (AOS), VMware vSphere and Nutanix Acropolis Hypervisor (AHV). You can also manage your Nutanix AHV clusters - live, with real-time metrics in the familiar ControlUp way (https://controlup97.document360.io/v1/docs/connecting-to-your-nutanix-ahv-hypervisor).

Network Connectivity

ControlUp data collection agents (ControlUp Console by default, or agents if explicitly designated) require https (tcp/443) access to the vCenter server or the XenServer pool master.

Hypervisor Permissions


Required vCenter permissions: the Read-Only role is sufficient for all monitoring purposes. If you want to use the built-in hypervisor-based VM power management functions, then you will need to create a custom role based on the Read-Only role, adding the following permissions:

  • In the Virtual Machine/Interaction category:
    • Power Off
    • Power On
    • Reset

vSAN Prerequisites

To retrieve vSAN metrics and metadata, refer to the vSan Prerequisites. article.

System Requirements for the ControlUp Data Collector

PowerShell minimum version 5.0 (with RemoteSigned execution policy)

  • VMware PowerCLI minimum Version 10.1.1.x (if needed, Ignore Invalid SSL Certificates)
  • .NET Framework 4.5 or higher

Example: Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Scope AllUsers

vSAN Requirements:

  • vSAN Performance service should be turned on
  • The user account configured for the hypervisor connection requires the "storage.View"

Citrix Hypervisor (XenServer)

If Active Directory authentication is enabled for the Citrix Hypervisor pool, the Read-Only role is sufficient. If you want to be able to use the built-in hypervisor-based VM power management functions, then you will need to upgrade the user role to ‘VM Operators’.


ControlUp requires for the user\service account to have Viewer only role for view-only capabilities (the user that you connect your Console to the hypervisor with). If you want to perform VM power management & host maintenance actions, you'll need to grant the user\service account with the Cluster Admin role.

To use a dedicated user\service account that you already have configured in your environment - you'll need to add your organizational Active Directory to Nutanix by going into Prism, Click the Gear Icon> Authentication. When you're finished with adding your AD - you can 'Test' the connection in ControlUp Real-Time Console and verify that it works.

If you don't want to connect your AD to your Nutanix cluster, you can create a local user in the Nutanix local management within Nutanix Prism. Click the Gear Icons > Local User Management and add the user with the proper role required.

Was this article helpful?

What's Next