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.

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 open an informational (non-technical) service request (SR) 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.

  • Your Horizon Cloud tenant record has the configuration option that allows you to activate the feature.
  • You have onboarded your Horizon Cloud environment to VMware Cloud Services Engagement Platform or integrated it with Workspace ONE. See Onboard Your Horizon Cloud Tenant to VMware Cloud Services Engagement Platform and VMware Cloud Services Using the Horizon Universal Console. To verify that this onboarding is completed, navigate to the General Settings page and verify that the Cloud Service Provider section displays Completed.
  • You must have completed the Active Directory registration steps in Performing Your First Active Directory Domain Registration in the Horizon Cloud Environment.
  • Your pod fleet has a pod capable of using the monitoring features.
    • For Horizon pods deployed on a VMware SDDC platform, the pod must meet the following requirements.
      • You have paired the pod with a Horizon Cloud Connector appliance running version 1.9.0.0 or later.
        Note: At this time, the Horizon Infrastructure Monitoring feature does not support Horizon pods in Azure VMware Solution (AVS).
      • You have configured the pod such that it can reach the DNS entries required by the Horizon Cloud Connector appliance. See the "DNS Requirements to Support Advanced Features" section in DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod.

        After onboarding your environment to VMware Cloud Services Engagement Platform and configuring the DNS entries for the pod, allow up to 20 minutes for the Horizon Cloud Connector appliance to complete the internal preparation tasks required for the Horizon Infrastructure Monitoring feature.

      • You have configured the pod's vCenter Server instance with the required statistics interval, as described in Statistics Collection Requirements for Horizon Pods.
    • For Horizon Cloud pods in Microsoft Azure, the pod must meet the following requirements.
      • The pod must be running manifest 2298.0 or later.

        The Horizon Infrastructure Monitoring does not support pods running manifests earlier than 2298.0.

      • The Microsoft Azure subscription that hosts the pod must accommodate the requirements of the Horizon Edge Virtual Appliance, as described in Horizon Edge Virtual Appliance Requirements for a Horizon Cloud Pod in Microsoft Azure.

        In the activation process, the system automatically deploys that appliance and configures the pod manager VMs for collection of the monitoring data. The Horizon Edge Virtual Appliance is a required element for using the infrastructure monitoring features with a pod in Microsoft Azure.

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.

Statistics Collection Requirements for Horizon Pods

To support infrastructure monitoring of a Horizon pod on a VMware SDDC platform, you must configure the required statistics interval for the pod's vCenter Server instance.

In the vSphere Client, navigate to the vCenter Server instance within the pod and then to the settings page for statistics intervals. Configure and enable a statistics interval with the following settings.

Table 1. Statistics Interval Settings for Infrastructure Monitoring
Attribute Value
Enabled On
Interval Duration 5 minutes
Save For 1 day
Statistics Level Level 4

For detailed instructions, go to the VMware vSphere Documentation page and search for the topic on how to configure statistics collection intervals.

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. (Horizon pod in a VMware SDDC only) Configure the pod's monitoring credentials as follows.
    1. In the console, from the Capacity page, open the pod's details page.
    2. Navigate to the tab for configuring credentials.
    3. Follow the on-screen guidance for adding the vCenter Server and Connection Server credentials used for pod monitoring. Take note of the following points:
      • Enter the appropriate user credentials and click Test to validate the credentials.
      • After the successful validation of the credentials, you must select the usage option for the Horizon monitoring feature.
      • (For vCenter Server credentials) At the minimum, you must add the credentials for the vCenter Server instance that hosts the pod's virtual desktops and workloads. If you use a different vCenter Server instance to host management components, you can also add the credentials for that instance.
  2. 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. Then follow the on-screen guidance for the pods you want to activate.
    • For a Horizon pod on a VMware SDDC platform, it can take up to 30 minutes to set up the required monitoring components on the Horizon Cloud Connector appliance after you have paired the appliance with the pod or updated the appliance version. The monitoring components must be set up before Horizon Infrastructure Monitoring can reach full activation on the pod.
    • For a Horizon Cloud pod in Microsoft Azure, 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.

Enabling Emails for Pod Infrastructure Alerts

Not every tenant gets access to this feature. If your tenant account is enabled for this feature, you can configure the system to automatically send an email when the Horizon Infrastructure Monitoring feature detects an issue with one of the participating pods. The email will be sent to the people who have the customer-admin role next to their names, as listed in the General Settings page's My VMware Accounts area. The email will contain information such as the pod ID, a description of the detected issue, and other helpful information.

  1. In the General Settings page's Monitoring area, open the settings.
  2. Follow the on-screen guidance to enable the Infrastructure Alert Email Notification.

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.