This article describes the system requirements and steps for activating the Horizon Infrastructure Monitoring feature for a pod in your Horizon Cloud environment. The feature enables the pod to report data about infrastructure issues to the Cloud Monitoring Service (CMS), giving you visibility into the health and status of the pod's components.

This feature is supported for use only with Horizon Cloud on Microsoft Azure deployments.

Note: Horizon Infrastructure Monitoring is currently unsupported for use with Horizon Cloud on Microsoft Azure pods in Azure China regions because access to the required packages.cloud.google.com site is disallowed from Azure China regions at this time.

Horizon Infrastructure Monitoring is currently unsupported for use with pods where proxy is configured.

You can activate the Horizon Infrastructure Monitoring feature from the Horizon Universal Console when VMware Support has configured your tenant account with support for the feature and after you have onboarded your Horizon Cloud environment with VMware Cloud Service Engagement Platform or integrated it with Workspace ONE. After you activate the feature for a pod, that pod reports infrastructure data to the CMS, which then sends the data to Horizon Universal Console.

Attention: As described in Tour of the Cloud-Based Horizon Universal Console, the console is dynamic and reflects features that are appropriate for the up-to-the-minute configuration of your tenant environment. Access to features described in this documentation can depend on factors including, and not limited to:
  • Whether the feature depends on system code available only in the latest Horizon Cloud pod manifest, Horizon pod version, or Horizon Cloud Connector version.
  • Whether access to the feature is in Limited Availability, as stated in the Release Notes at the feature's debut.
  • Whether the feature requires specific licensing or SKUs.

When you see mention of a feature in this documentation and you do not see that feature in the console, first check the Release Notes to see if the feature's access is limited and the way you can request enablement in your tenant. Alternatively, when you believe you are entitled to use a feature that is described in this documentation and you do not see it in the console, you can ask your VMware Horizon Cloud Service representative or, if you do not have a representative, you can file a service request (SR) to the Horizon Cloud Service team as described in How to file a Support Request in Customer Connect (VMware KB 2006985).

Prerequisites to Activating Horizon Infrastructure Monitoring for a Pod

To support the activation workflow for Horizon Infrastructure Monitoring, your Horizon Cloud environment must meet the following criteria.

When your Horizon Cloud environment meets all the prerequisites, the console displays an instructional banner that directs you to the console location for activating the pod monitoring feature.

Horizon Edge Virtual Appliance Requirements for a Horizon Cloud Pod in Microsoft Azure

When you use the console to activate Horizon Infrastructure Monitoring on a Horizon Cloud pod in Microsoft Azure, the system:

  1. Creates a resource group in the pod's subscription in Microsoft Azure.
  2. Instantiates and configures the Horizon Edge Virtual Appliance and its required artifacts: NIC, NSG, VM, disk. Connects the appliance's NIC to the pod's management subnet.
  3. Configures the pod manager VMs for the collection of the monitoring data that the appliance can collect.

To ensure a successful process, verify that each Horizon Cloud pod undergoing the activation meets the following requirements.

  • Ensure that the Microsoft Azure subscription has enough capacity for the appliance. This appliance requires the Standard_D4_v3 VM size.
  • Ensure that the management subnet meets the DNS requirements for the appliance. The appliance sends the monitoring to the CMS. See the appropriate table rows for the Horizon Infrastructure Monitoring and Horizon Edge Virtual Appliance in DNS Requirements for a Horizon Cloud Pod in Microsoft and Related Service Features.
  • Ensure that the pod meets the necessary ports and protocol requirements. Traffic is required between this appliance and the pod manager VMs, and between this appliance and the cloud control plane, both during activation of this feature on the pod and during steady-state operations to collect the monitoring data. See the Horizon Edge Virtual Appliance section in Ports and Protocols Requirements for a Horizon Cloud Pod.
  • Ensure that you have zero IP range conflicts in the pod manager's VNet and management subnet with the IP range of 10.32.0.0/12 (10.32.0.1 - 10.47.255.254). This IP range is used for underlying Kubernetes networking on the appliance. If your pod has any IP conflicts with that range, contact VMware Support to get help with activating pod monitoring on that pod.
  • If the service principal you are using for the pod has a custom role instead of using the Contributor role, ensure that the custom role can perform the operations required by Horizon Cloud, as documented in Operations Required by Horizon Cloud in Your Microsoft Azure Subscriptions.

Activation Procedure

  1. Go to the console page to which the Horizon Infrastructure Monitoring banner directs you, locate Horizon Infrastructure Monitoring and make the on-screen selection for managing the monitoring.
    • The system starts deploying the Horizon Edge Virtual Appliance into that pod's subscription, as described in the preceding sections. The overall deployment and configuration process of that appliance can take up to 30 minutes typically.

The console's Horizon Infrastructure Monitoring section will indicate when the activation process is completed successfully. If the screen indicates that monitoring enablement has failed, you must contact VMware Support for assistance.

The activation process is irreversible. Once you activate Horizon Infrastructure Monitoring on a pod, you cannot deactivate the feature on that pod.

Important: After the console displays the message that the activation is completed successfully, you must wait longer before the monitoring data from the pod can be made available in the Dashboard page's Issues side tab and in the Infrastructure tab. The expected wait time is about 20 minutes.

Using the Horizon Universal Console to View the Pod Monitoring Data

The console displays pod infrastructure monitoring data in the Dashboard page's Infrastructure tab. In addition, the Dashboard page's Issue tab displays short description of the current top issues from the pods.

For more information about using the Dashboard page's Infrastructure tab to view information about the issues reported by the Horizon Infrastructure Monitoring feature, see the relevant section in Horizon Cloud Dashboard - Health Visibility and Insights into Your Pod Fleet and Tenant Environment.