Before you can obtain the data that gives you the ability to monitor capacity, usage, and health within and across your first-gen tenant's fleet of cloud-connected pods, the Cloud Monitoring Service (CMS) must be enabled. CMS is one of Horizon Cloud's central services. The CMS is enabled at a tenant level, and its setting applies for all of the pods that are connected to that first-gen Horizon Cloud tenant.

The Cloud Monitoring Service (CMS) collects and stores session, application, and desktop data from cloud-connected pods for monitoring and reporting purposes. The data is presented in various console locations, as described in First-Gen Tenants - Introducing the Cloud Monitoring Service's Unified Visibility and Insights, Health Monitoring, and Help Desk Features Provided in the Horizon Universal Console.

Tip: The CMS is typically turned on by default at your first use of your Horizon Cloud tenant. If you are not seeing visual data displayed on those console pages, first follow these steps below to confirm that the CMS is turned on in the General Settings page.

When the Cloud Monitoring Service is enabled for your tenant, you can also optionally choose to opt in or opt out of tracking user information related to your end users' sessions. Typical information that CMS collects about user sessions includes the times they logged in, session durations, and average session length per user.

  • When you opt in to the collection of user data, the service collects this information and maintains it for the duration of your use of your first-gen Horizon Cloud environment. As described in VMware KB article 91183, this data is made available in Workspace ONE Intelligence. If you decide later that you do not want to collect user data, you can stop the collection and also delete any collected data by switching off the Session Data toggle.
  • When you opt out of the collection of user data but leave the monitoring service enabled, the service collects session data for a limited period and hashes the user name to allow real-time administration while deactivating the historical and aggregated viewing of information. As a result, some reports, such as the Horizon User Usage report, are unavailable. In this case the system also continues to collect other data related to applications and desktops in connected pods.

Switching off these toggles also deletes any data that was previously collected. Switching off the Session Data toggle by itself deletes the previously collected user-related data, and leaves the other types of collected data, such as the pod-level and session-related data. Switching off the Cloud Monitoring Service toggle deletes all collected data for your tenant.

Caution: If you have cloud-connected Horizon pods that are sending desktop data to vRealize Operations Manager, enabling CMS causes data to be sent to the Cloud Monitoring Service instead. To continue using vRealize Operations Manager to collect that desktop session data, deactivate CMS.

Prerequisites

Before you can activate the Cloud Monitoring Service for any of your cloud-connected Horizon pods or pods in Microsoft Azure, you must have at least one pod in your tenant's pod fleet.

Procedure

  1. Navigate to the console's General Settings page by clicking Settings > General Settings.
  2. Scroll down the page to locate the Monitoring section.
  3. Click the pencil icon to change the settings.
    • Use the Cloud Monitoring Service toggle to activate or deactivate all of the data collection for your tenant environment. When deactivated, the CMS does not collect any data from your entire fleet of cloud-connected pods in that tenant environment.
    • Use the Session Data toggle to opt in or opt out of tracking user information related to your end users' sessions.
  4. Click Save to save your changes.