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 and the agent-running VMs reside.

Brief Introduction

The Cloud Monitoring Service obtains capacity, health, and usage-related data from the pods in your tenant's fleet and from the 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.

For deployments which are configured with the Horizon Infrastructure Monitoring feature, data from Horizon Infrastructure Monitoring also flows to the CMS, and subsequently flows into the Dashboard page's Infrastructure tab.

Using CMS Features in the Horizon Universal Console - Requirements

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:

  1. One cloud-connected pod.
  2. A completed Active Directory domain registration for at least one Active Directory domain to which that pod has line of sight.
  3. The Super Administrators role assigned to at least one group in that Active Directory domain.
  4. 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 (CSMS). For more information, see Manually Activate Services in version 1.8 or 1.9.

    If your Horizon pod is cloud-connected using Horizon Cloud Connector in a native Amazon EC2 deployment, the CMS is enabled for that pod only if you manually activated the Connection Server Monitoring Service (CSMS) in the appliance. For more information, see Manually Activate Services for Horizon Cloud Connector on Native Amazon EC2.

The types of pods that you can onboard to the control plane are described in Horizon Cloud - Introduction to the Service.

Horizon Deployments - Requirements

Use of the CMS with these deployment types has these requirements.

  • The deployment 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.

  • The Horizon deployment — pod and desktops — must be done according to one of the supported Horizon pod deployment architectures in the Horizon reference architecture. Refer to Horizon reference architectures in VMware Tech Zone's VMware Workspace ONE and VMware Horizon Reference Architecture site.

When you have cloud-connected Horizon pods that are sending desktop data to vRealize Operations for Horizon, enabling CMS causes data to be sent to the Cloud Monitoring Service instead. To remain using vRealize Operations for Horizon to collect desktop session data, deactivate CMS. Alternatively, you can use the Management Pack for Horizon for vRealize Operations Manager with CMS enabled.

Horizon Cloud on Microsoft Azure Deployments - Requirements

Availability of CMS data in the user card and reports for Horizon Cloud on Microsoft Azure deployments depends on whether you have the CMS enabled in your Horizon Cloud tenant and which options you selected when installing the agent software on the deployment's desktops 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.
Note: The RDP protocol provides for a limited set of metrics when compared with the other protocols supported in Horizon Cloud. The vRealize Operations Desktop Agent will return data for those metrics that the RDP protocol provides.

CMS and Historical Session Data

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-related 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.

Learn More

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.