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. Whether a cloud-connected pod lives on-premises, in VMware Cloud on AWS, or in Microsoft Azure, the Cloud Monitoring Service obtains the capacity, health, and usage-related data from the pod and presents that data to you within the Horizon Cloud Administration Console. That 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.
Before you can use the console for all of 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 enabling or disabling 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.
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:
- High-Level Workflow When You are Onboarding an Existing Manually Deployed Horizon Pod as Your First Pod to Your Horizon Cloud Tenant Environment
- High-Level Workflow for When Your Very First Horizon Cloud Cloud-Connected Pod is from Using the Pod Deployer to Deploy a Pod into Microsoft Azure
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.