The Cloud Monitoring Service (CMS) is one of the central services provided in Horizon Cloud. The CMS gives you the ability to monitor capacity, usage, and health within and across your fleet of cloud-connected pods, regardless of the deployment environments in which those individual pods reside. Wherever your cloud-connected pods and the agent-running VMs live — whether in your private data centers or in industry cloud capacities — the Cloud Monitoring Service obtains the capacity, health, and usage-related data from those pods and agent-running VMs. The CMS presents that data to you within the Horizon Universal Console. This console is your single pane of glass for working with your tenant's fleet of cloud-connected pods. The CMS feeds data into the various Dashboard page's tabs to help you see overall health and drill-down into the health, capacity, and usage metrics at various levels. The CMS also provides the data for many of the reporting views within the console's Reports page, as well as within the user cards, in which you perform help desk operations to support your individual end users. Data from the Horizon Infrastructure Monitoring feature also flows to the CMS, and subsequently flows into the Dashboard page's Infrastructure tab.
Requirements Specific to Horizon Pods
The CMS requires that the instances for the Horizon Connection Server and the Horizon Cloud Connector reside in a VMware SDDC-based environment. A VMware SDDC-based environment is an environment such as vSphere, VMware Cloud on AWS, or Azure VMware Solution.
As described in the Horizon 7 version 7.13 Release Notes, you can now run a Horizon pod's virtual desktops that run on Hyper-V hypervisor. As long as your Horizon pod meets the requirement of having the Horizon Connection Server and Horizon Cloud Connector instances in a VMware SDDC-based environment, the standard CMS features that relate to data reported from the virtual desktops are supported for such virtual desktops that reside on all supported third-party hypervisors. For information about the currently supported third-party hypervisors for this use case, see the Horizon documentation at Horizon 7 Documentation and Horizon Documentation.
To support the use of the CMS, the Horizon pod must meet the following requirements.
- The pod must be running Horizon 7 7.9 or later.
- The pod's JMS message security mode is set to Enhanced. The CMS features do not work if the mode is not set to Enhanced.
Use the administrator console for the pod to check the security mode setting. If needed, change the security mode to Enhanced, as described in the "Change the JMS Message Security Mode to Enhanced" topic in Horizon 7 Upgrades from the VMware Horizon 7 Documentation.
Requirements for Using CMS Features in the Console
Before you can use the console for the visibility, health monitoring, and help desk features that the CMS provides, you must have in your tenant environment a minimum of the following:
- One cloud-connected pod.
- A completed Active Directory domain registration for at least one Active Directory domain to which that pod has line of sight.
- The Super Administrators role assigned to at least one group in that Active Directory domain.
- The Cloud Monitoring Service (CMS) enabled for your tenant environment. The console's General Settings page provides the switches for activating or deactivating the CMS for your Horizon Cloud tenant environment. The same switch controls the use of CMS for all of the cloud-connected pods in the same tenant environment. See Customizable General Settings for Your Horizon Cloud Tenant Environment.
If your Horizon pod is cloud-connected using Horizon Cloud Connector 1.8 or 1.9, the CMS is enabled for that pod if you deployed Horizon Cloud Connector with the Full Feature profile or if you deployed with the Basic Feature profile and then manually activated the Connection Server Monitoring Service. For more information, see Manually Activate Horizon Cloud Services for Horizon Cloud Connector 1.8 or 1.9.
The types of pods that you can connect to Horizon Cloud are described in Introduction to Horizon Cloud and Onboarding Pods to Become Cloud-Connected Pods. For the high-level steps needed to get useful cloud-connected pods that can leverage the Cloud Monitoring Service, see the suggested workflow for the pod type you want:
Required Horizon Agents Installer (HAI) Options
Availability of CMS data in the user card and reports depends on whether you have the CMS enabled in your Horizon Cloud tenant and which options you selected when installing software using the Horizon Agents Installer (HAI).
- To display historical session data, you should enable CMS and install the vRealize Operations Desktop Agent in HAI.
- To show live session data, you should also install the Help Desk Plugin in HAI.
Historical session data refers to data such as:
- Session information for logged-off sessions over the previous seven days.
- Performance trend data (CPU, memory, latency, disk trend) for active, idle, and disconnected sessions over the previous 15 minutes.
When your CMS options are configured such that live session data is not collected and displayed, you will see VM-relative information and login time breakdowns, but will not see:
- Client information.
- User experience information.
- Real-time performance trends.
- Process/Application information.
You set the CMS's session data option using the console's General Settings page.
Use the following topics and their subtopics to learn about the unified visibility, health monitoring, and help desk features that the Cloud Monitoring Service provides.