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 first-gen 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: This information applies solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.
As of August 2022, Horizon Cloud is generally available and has its own guide, Using Horizon Control Plane.
An indication of which environment you have,Horizon Cloud or first-gen, is the pattern that appears in the browser's URL field after you log in to your environment and see the Horizon Universal Console label. For aHorizon Cloud environment, the console's URL address contains a portion like /hcsadmin/. The first-gen console's URL has a different section (/horizonadmin/).
Before You Read this Page
Before you read this page, please take consideration of the following points.
Note: As described in KB article 93762, the Horizon Infrastructure Monitoring feature has been deprecated and first-gen tenants can no longer activate or use that feature. As of October 2023, the information in this page that previously related to that deprecated feature has been updated accordingly.
With deprecation of that feature, the console's Dashboard no longer displays an Infrastructure tab.
Note: As of June 30, 2023, this documentation page is updated to match with the changes to the first-generation console as described in KB article 91183.
- With these changes, the first-gen console's Dashboard UI is updated to provide access to real-time data only in Dashboard's Overview tab's Utilization area and Sessions area.
- Please note that if your first-gen tenant has deactivated monitoring user session data, the reports associated with utilization, trending, and historical analysis are deactivated and then unavailable in Omnissa Intelligence. When the monitoring is deactivated, the system collects such user session information for a limited period of time and hashes the user name to enable real time administration while deactivating historical and aggregated viewing of that user information. As a result, the reports that would display historical and aggregated viewing of that data, such as the Sessions report, will be unavailable. For the way to check if your tenant has this monitoring deactivated, navigate to the console settings in Settings > General Settings > Monitoring.
For further information, see Experience Management for Horizon, Horizon Cloud First-Gen Integration, and Access Horizon Cloud Data in Intelligence Reports.
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 first-gen Horizon Cloud environment and presents the data for your use.
The system refreshes the information every few minutes. You can also refresh the page manually.
Important:
For pods deployed into Microsoft Azure, the displayed information does 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:
- In the process of deploying and connecting the pod to Horizon Cloud, you specified a city name.
- For all pods, according to the city name specified for the pod's associated location in its pod details. To associate a location with an already onboarded pod, see Horizon Cloud - Change Some Cloud-Related Characteristics for a Cloud-Connected Pod By Using the Capacity Page's Edit Workflow
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, when the pod is online, 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 Control Plane Service. If the pod is offline, the link to launch its Horizon Console is unavailable until the pod is reachable again.
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 Control Plane Service.
- The Delivery tab lists issues related to components of the pod itself, such as the Connection Server.
-
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. 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 Control Plane 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 real-time 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 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 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 vSphere-based 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 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
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.
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 Horizon certified Thin Client or Zero Client to access the desktops and applications in cloud-connected Horizon pods of old, no-longer-supported version 7.7.
Was this page helpful?