The Horizon Universal Console provides the Dashboard page as your one-stop place from which you can get a visual sense of the overall health of your entire fleet of cloud-connected pods, as well as access real-time metrics and health information for all of the pods in your Horizon Cloud tenant environment. The data is provided by the Cloud Monitoring Service (CMS), which is one of the central services in Horizon Cloud. The Dashboard page is available from the console's Monitor icon.

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

Dashboard - Introduction

Use the Dashboard page's Overview tab to get a snapshot health view for what is happening in your entire fleet of cloud-connected pods, and then optionally drill-down to see more details. The Cloud Monitoring Service, one of Horizon Cloud's central services, provides the data that you see on the Overview tab. The CMS obtains this data from all of the cloud-connected pods in your Horizon Cloud tenant environment and presents the data for your use.

Note: The charts of session data depict historical data and trends only when the Cloud Monitoring Service feature is enabled for your Horizon Cloud environment. That feature collects and stores session, application, and desktop data from cloud-connected pods for monitoring and reporting purposes. When the Cloud Monitoring Service feature is deactivated for your environment, historical data is not collected and therefore not available to display. In that case, the charts of session data you see are based on data from current sessions only. The Cloud Monitoring Service feature is active by default. If the feature is not activated in your environment and you want to use the service to collect session data over time, use the console to activate the feature. See Enabling or Deactivating the Cloud Monitoring Service (CMS) for Your Horizon Cloud Tenant Environment.

The following screenshot illustrates the Overview tab with four cloud-connected pods. The screenshot depicts two pods using Microsoft Azure capacity, one on-premises Horizon pod, and one Horizon pod using VMware Cloud on AWS capacity. The on-premises Horizon pod is located in Paris, and is reporting two issues.


Screenshot of the Dashboard page

The system refreshes the information every few minutes. You can also refresh the page manually.

Important:

For pods deployed into Microsoft Azure, these reports do not reflect user-related data until an hour has passed from the time you deployed the pod or from the time you enabled monitoring user session information.

Global Footprint

The upper portion of the Dashboard page contains the interactive Global Footprint. This footprint map visually depicts your pods' geographic city locations and shows additional information when you hover on a location. The map supports the typical industry-standard map interactivity features, such as panning and zooming in or out to view the map at different scales. Zooming in for more detail is especially useful to see those pods which are clustered together at the same location. When you first display the map, the zoom defaults to a scale that will show your pod fleet in a single view.

When your environment has pods of different types, you can use the filter function at the bottom right of the map area to selectively show or hide pods of specific types.

Important: The system uses the location information that is associated with the pod from one of the following ways: The system uses its city lookup table to get the latitude and longitude coordinates associated with the specified city, and places the pod at those coordinates on the map.

Select one of the issue- or session-related tabs to the right of the map to select a specific view of the footprint map. Based on the view selected, the pod icons on the map depict health-related (issues) data or session-related data. Hover over the pod icons and the console displays additional relevant details.

Issue-related
With this view selected (the default), the footprint map indicates each pod's health. Each main visual icon represents the set of pods at that geographic city location along with the total number of pods there. Hovering over an icon displays a list of the pods at that location, along with an icon indicating the type of pod and a green dot indicating a healthy deployment or a red dot indicating an unhealthy deployment of that pod. Clicking on the VIEW link in that pod list opens the page that shows detailed information for issues reported for the pods at that location.

The area to the right of the map shows the total number of current issues at the top and lists the top five issues below. Hovering on an issue in this area opens the pod information pop-up on the map for the location where the issue is occurring. For Horizon pods, the pod name is a link that you can click to launch Horizon Console for that pod's Horizon Connection Server, as described in Launch Horizon Console as a Cloud Service. Clicking on the VIEW link at the bottom of the issue list opens a page to see more detailed data. That page has various tabs and various sorting and filtering options.

  • The Total Issues tab lists all of the issues and details about each one, such as which pod has the issue, the pod type, and so on. For Horizon pods, the pod name is a link that you can click to launch Horizon Console for that pod's Horizon Connection Server, as described in Launch Horizon Console as a Cloud Service.
  • The Delivery tab lists issues related to components of the pod itself, such as the Connection Server.
  • The Infrastructure tab lists issues related to pod-based components and non-pod components — those that are used in tandem with a pod, such as your Active Directory domain, NTP service, the Microsoft Azure service, and so on. Data about a pod's infrastructure components is provided in this tab only when the pod infrastructure feature is enabled for that pod.
  • The User Experience tab lists issues related to user experiences.
Session-related (VDI & RDSH sessions)
With this view selected, the footprint map indicates each pod's session-related data. Each main visual icon represents the set of pods at that geographic city location along with the total number of sessions in those pods. This total includes connected, active, and idle sessions. Hovering over an icon displays a list of the pods with an icon indicating the type of pod and displays session data. If the Cloud Monitoring Service feature is enabled, the pop-up displays the session trend and session count details for the pods at that location. If you have deactivated the Cloud Monitoring Service feature, the pop-up displays a pie chart of current sessions by session type and the session count details for the pods at that location. Clicking on the VIEW link under the list of pods opens a page to see more detailed session-related data for that location. That page contains a chart for each session type showing sessions by status and a list of sessions with detailed information for each. The list of sessions displayed can be filtered by location and pod. There are also sort and filter functions for each column of information.

The area to the right of the map shows the total number of end-user sessions for your pods. This total includes connected, active, and idle sessions. It then lists the pods with the number of sessions for each. Hovering on a pod in the list opens the information pop-up on the map for the location where that pod is located. For Horizon pods, the pod name is a link that you can click to launch Horizon Console for that pod's Horizon Connection Server, as described in Launch Horizon Console as a Cloud Service. Clicking on the VIEW link at the bottom of the pod list opens a page to see more detailed data. That page provides various sorting and filtering options, and contains charts that depict session-related data based on the selected sorting and filtering options.

Dashboard - Utilization Area

The Utilization area on the dashboard's main overview displays interactive graphs that depict the system's calculation of the utilization of your pod fleet's resources, aggregated by pod type. The system's calculation and meaning of the utilization data that it depicts in these graphs varies depending on the pod type. You can interact with each graph by clicking and hovering to see more details.

Horizon Cloud pods in Microsoft Azure — the pod-manager-based pod type
For pods of this pod type, the Utilization graph displays those pods' allocated capacity and their utilization of allocated desktops and RDS-based remote applications. This data is intended for administrators, to help in understanding whether enough desktops are allocated for the end users' use of their entitled desktops and applications. In the charted data, the overall capacity percentage is updated once an hour. The capacity percentages for the desktop and application sessions is updated every hour.

By default, the charted data is:

  • The last 24 hours of data. One point corresponds to one hour.
  • Data averaged over your fleet's pods of this pod type within the last 24 hours, on an hourly basis.

The system's definition of utilization is the number of active sessions divided by the maximum possible number of sessions (ActiveSessions / MaxPossibleSessions).

Horizon pods deployed in VMware SDDC — the Connection Server pod type
For pods of this pod type, the Utilization graphs displays the maximum values for average CPU, memory, and disk storage use.

By default, the charted data is:

  • The last 24 hours of data. One point corresponds to one minute.
  • Data averaged over your fleet's pods of the corresponding pod type within those 24 hours, on a minute-by-minute basis.

Dashboard - Sessions Area and Tab

The Sessions area on the dashboard's main overview depicts the breakdown of active and idle sessions for all of your pods' VDI desktops, RDSH desktops, and RDSH applications. The outcome of clicking VIEW in the Sessions area displays the dashboard's Sessions tab. Within the Sessions tab, you can drill down into the CMS-provided detailed data about your pod-provisioned end-user sessions.

Tip: The console displays this tab above the footprint map only when the Cloud Monitoring Service feature is enabled in your environment. The Cloud Monitoring Service feature is activated by default. If the feature is not enabled in your environment and you want to use the service to collect session data over time, use the console enable the feature. See Enabling or Deactivating the Cloud Monitoring Service (CMS) for Your Horizon Cloud Tenant Environment.

The top of the Sessions tab shows total numbers for sessions and users. The rest of the tab contains several charts representing detailed information about the sessions in your environment.

  • You can filter this data by time period, location, deployment type, pod, and pool.

    In the Pods filter, selecting All Pods shows session distribution across different pods, and selecting a particular pod shows session distribution across different pools in the selected pod. In both cases, the two colors in each bar represent current session count and remaining unused session count.

  • Pointing to chart elements (trend lines, bars) displays numerical data.
  • Clicking the View link in the bottom left of any of these charts opens a list page that shows a detailed breakdown of the chart data. These pages also indicate the status of each session or VM: green for normal, yellow for warning, or red for critical.

The following table describes the intent of the more complex charts. In addition to the charts mentioned in this table, the Sessions tab provides various additional charts for data related to VM utilization, disk latency, logon duration, and protocol latency. Use the on-screen guidance and on-screen informational tooltips to learn about each chart.

Chart Description
Count by Session Status Trend lines showing number of sessions over time by session status (Total Sessions, Active, Idle, Disconnected).
Resource Consumption Use the drop-down menus in the upper right of the chart to select the resource (CPU, Memory, IOPS) and deployment type.
Horizon Cloud pods in Microsoft Azure — the pod-manager-based pod type
The trend lines show resource consumption over time by session type (Total Sessions, Total Desktop Sessions, Total Application Sessions). To the right of the trend line chart is a bar showing the number of sessions per pod (if data for multiple pods is shown) or number of sessions per assignment/farm (if data for a single pod is shown).
Horizon pods — the Connector Server pod type
The trend line shows resource consumption over time for all sessions. To the right of the trend line chart is a pie chart showing resource utilization per pod (if data for multiple pods is shown) or resource utilization per pool/farm (if data for a single pod is shown).
Note: You can also see detailed information for resource consumption in the CPU Utilization, Memory Utilization, Disk IOPS Utilization charts.

Dashboard - Connection Statistics Area

This area displays the breakdown of the protocols, Horizon client types, and forms of network access in use by end-user connections to all of your pods.

The Horizon Client chart includes a type labeled Other. The system labels a connection as Other when:

  • The connection is using an older version of the Horizon Agent that cannot report the client type.
  • The connection is using a VMware-certified Thin Client or Zero Client to access the desktops and applications in cloud-connected Horizon 7 version 7.7 pods.

Dashboard - Users Tab

The Users tab displays detailed information about your users and issues they are encountering. Within the Users tab, you can drill down into the CMS-provided detailed data.

Tip: The console displays this tab above the footprint map only when the Cloud Monitoring Service feature and its option to collect specific per-user session data are both enabled in your environment. That feature and option are activated by default. If they are not in your environment and you want to use the service to collect the per-user data over time, use the console to enable the feature and the per-user session data option. See Enabling or Deactivating the Cloud Monitoring Service (CMS) for Your Horizon Cloud Tenant Environment.

Use any provided on-screen guidance and on-screen informational tooltips to learn about each chart. The Users tab has various filtering options that apply to what is displayed on the Users tab itself. As you use the various VIEW options to click through and view details for each chart, those individual pages also have various sorting and filtering options.

On this tab, the system depicts three main types of user-related issues. If any of the following metrics are out of the acceptable range, the system counts it as a user having an issue.

Issue Type Definition
Latency Disc latency is outside acceptable range.
Protocol Protocol latency or packet loss is outside acceptable range.
Slow Logon Logon duration is outside acceptable range.

At the top of the Users tab are what the system considers to be global metrics.

Unique Users Total unique users. This value includes active, idle, and disconnected sessions.
User Sessions

Total sessions. This value includes active, idle, and disconnected sessions.

Active Sessions Total active sessions.
Issues Number of users impacted by user experience related issues.

The following list describes the intent of the more complex and interactive charts. Use any on-screen guidance and on-screen informational tooltips to learn more about each one. Clicking View displays the data as a list with more detailed information related to each record that is depicted in the parent chart.

User Distribution chart
This bar chart shows the distribution of users impacted by issues across pods, pools, or assignments.
  • If you have All Pods selected in the pod filter at the top of the tab, the chart shows users by pod. Clicking the bar for a pod changes the pod filter to select that pod. The tab then shows data only for that pod, and the User Distribution chart shows only users in that pod, broken down by pool.
  • If you have a particular pool selected in the pool filter at the top of the tab, the tab shows data only for that pool, and the User Distribution chart shows only users in that pool.
Users by Consumption chart
List of users by consumption of resources. A drop-down menu provides for choosing the type of resource to depict (CPU, Memory, or Disk IOPS). Pointing to the value in the Utilization by Sessions column displays the utilization value. Clicking View displays data listing page, with an additional filter at the top of the page for filtering the data according to a particular resource (CPU, Memory, or Disk IOPS). On that listing page, you can also click the value in the Sessions column to view session details for the user.
Issues chart
Bar chart showing the number of affected users broken down by type of issue (Latency, Protocol, Slow Logon). Clicking View displays a data listing page, with an additional filter at the top of the page provides for filtering the data according to a particular issue type (Latency, Protocol, Slow Logon). On that listing page, clicking a bar for a particular issue type in the chart sets the issue type filter to that type, so that only those issues are shown. The bottom of the listing page is intended to display the values for the main metrics (Disc Latency, Protocol Latency, and Login Duration), along with values for Bandwidth, Frame Rate, and Packet Loss.

Dashboard - Infrastructure Tab

The Infrastructure tab displays detailed information about the pods' infrastructure — data about the various pod components. Within the tab, you can drill down into the CMS-provided detailed data.

Tip: The console displays this tab above the footprint map only when both of the following conditions are met:

Even when the preceding conditions are met and you see this tab displayed above the footprint map, before the console will display data in this tab, you must have at least one pod fully activated for pod infrastructure monitoring. The pod infrastructure monitoring feature provides for sending the data to the CMS, which then provides the data to the console for display. See Horizon Infrastructure Monitoring and the Pods in Your Horizon Cloud Environment.

The monitoring data obtained from the pods that are fully activated for this monitoring is displayed in this tab. Colored dots indicate the health of the various pod components which this monitoring feature supports. Click a dot to drill down into further details. Some examples of the types of data that can be displayed are machine status, CPU usage, memory usage, and disk usage. Within the subsequently displayed page are data graphs and tiles that present the data. The status of connected services such as a pod's Active Directory, DNS, and others is also collected and displayed. Continue to use the displayed hyperlinks to drill down into the data for specific areas. Use the provided filters to change the view of various items.

Note: If all the Connection Server instances in a Horizon pod go offline, the Infrastructure tab displays that pod's Horizon Cloud Connector appliance as offline.