vSphere Infrastructure Observability for Horizon 8

Omnissa Monitor provides a unified view of your vSphere and Horizon 8 infrastructure. From a single interface you can connect data sources, monitor host and VM health, track resource utilization, and identify issues before they affect end users.

Supported Versions and Limitations

• The minimum supported vSphere/vCenter version is 8.0.
• Each data collector supports monitoring one vSphere environment.

Navigating the interface

The left-hand navigation panel is available on every screen and provides access to all major sections of Omnissa Monitor.

Overview (Home)

The Overview is the first screen displayed after login. It provides a high-level snapshot of your entire Omnissa Monitor environment.

The Data Sources section displays a summary card for each connected source:

Each card includes a View details link to that source's detail page.

Note: Data sources that are not connected do not appear in the Connected sources section. See Connecting a vSphere data source to add one.

Data Sources page

The Data Sources page is where you link external infrastructure environments to Omnissa Monitor. Once connected, data flows into the dashboards and health views.

Viewing connected sources

Navigate to Data Sources in the left panel. The page contains two sections:

• Connected sources: environments already linked to Omnissa Monitor. Each card shows the source name, a summary metric (such as the number of connected pods or vCenters), and a View details link.
• Available sources: sources available to connect.

Connecting a vSphere data source

Prerequisite: A data collector must be configured and running before you connect a vCenter. You can use the same data collector that is already configured for your Horizon 8 pod — a separate collector is not required.

Fields marked with an asterisk (*) are mandatory.

1. Open the Connect vSphere form. On the Data Sources page, locate the vSphere card under Available sources and click Connect.

2. Enter vCenter credentials.

   Field	Description
   Data Collector *	The data collector that will communicate with this vCenter. Can use the same data collector as the associated Horizon Pod.
   vCenter Server name *	Display name for this vCenter within Omnissa Monitor
   vCenter Server FQDN *	Fully qualified domain name of your vCenter Server (for example, vcenter.yourdomain.com)
   Username *	Username for authenticating with the vCenter
   Password *	Password associated with the username

3. Save the connection. Click Save. Omnissa Monitor validates the credentials and establishes the connection.

4. Verify the connection. After saving, you are redirected to the vCenters page. Confirm your new vCenter appears and review its status:

   Column	Description
   vCenter name	Display name assigned during setup
   Connectivity status	Connected if Omnissa Monitor can reach the vCenter
   Certificate status	Valid, Expiring, or Expired — the state of the vCenter's SSL certificate
   FQDN	Fully qualified domain name of the vCenter Server
   Last data received	Timestamp of the most recent data ingestion

   Note: Renew an Expiring certificate promptly to avoid interrupting data collection. An Expired certificate halts data collection until the certificate is renewed and the connection is refreshed.

5. Confirm on the Data Sources page. Navigate back to Data Sources. The vSphere card now appears under Connected sources and displays the number of connected vCenters.

Additional actions available on the vCenters page:

vSphere dashboards

The vSphere dashboards provide views for monitoring the health and performance of your vSphere infrastructure. Access them from vSphere dashboards in the left navigation.

vSphere Overview dashboard

The vSphere Overview dashboard summarizes the entire vSphere environment in four sections.

Summary metrics: three aggregate counts displayed at the top of the page:

• Clusters: total number of monitored vSphere clusters
• Hosts: total number of ESXi hosts across all clusters
• Virtual machines: total number of virtual machines

Top issues: the Issues by category bar chart ranks problem areas by issue count, helping you identify where attention is needed.

Infrastructure health: two donut charts summarize health:

• Hosts health status: host count by health state (green for healthy, yellow for warning, red for critical)
• VMs health status: VM count by the same health states

Click View details beneath either chart to open the corresponding health status detail view.

Resource utilization: stacked horizontal bar charts display resource consumption:

• Hosts: CPU and memory utilization by band (low, medium, high, very high)
• VMs: CPU and memory utilization using the same bands

Use the filter controls above each chart to narrow results. Click View details to open the full utilization tables.

Note: Charts can be filtered by vCenter and time period. Some charts also offer an aggregation option — minimum, maximum, or average.

Hosts dashboard

The Hosts dashboard provides detailed performance metrics for all ESXi hosts in your environment.

A row of summary tiles at the top of the page counts hosts currently showing signs of performance degradation. For example, hosts with high CPU utilization, high CPU contention, high memory utilization, or high memory contention. Use these tiles as a starting point for identifying which hosts need attention.

Bar charts display the following host-level metrics:

• CPU utilization
• Memory utilization
• CPU contention
• Memory contention
• Disk latency
• Datastore space

Each chart supports attribute filtering and includes a View details link that opens a full drill-down view.

Hosts CPU utilization detail view

Displays a stacked bar chart of CPU utilization across hosts and a sortable table with these columns:

• Host name
• Cluster
• CPU contention
• Effective CPU and effective memory
• Number of VMs and number of powered-on VMs
• CPU cores and CPU threads

Use the Search bar to filter by host name, and Manage columns to adjust the view.

Hosts health status detail view

Combines a donut gauge showing overall host health distribution with a full table of all hosts. Table columns include:

• Host name (linked to a detail page)
• vCenter name
• Connectivity status (Connected or Disconnected)
• Health status
• Certificate status (Valid, Expiring, or Expired)
• Certificate expiration date
• FQDN
• Number of VMs, CPU utilization, memory utilization, disk utilization

Use Refresh to update the data and Manage columns to customize the table.

Virtual Machines dashboard

The Virtual Machines dashboard mirrors the structure of the Hosts dashboard but focuses on VM-level performance. Charts include:

• CPU utilization
• Memory utilization
• CPU contention
• Network utilization
• Net packet drop
• Disk latency

VMs CPU utilization detail view

Displays a bar chart of CPU utilization across VMs and a table with these columns:

• VM name
• Username
• Login time and logon duration
• Session duration
• CPU utilization, memory utilization, net packet drop, disk drives

VMs with a Connected status are shown with a green indicator.

VM health status detail view

Displays a donut gauge of overall VM health alongside a detailed table of all virtual machines. Table columns include:

• VM name
• vCenter
• Login time and logon duration
• Session duration and session health type
• Desktop type

Health states are color-coded: green (healthy), yellow (warning), and red (critical).

Tips and best practices

Keep certificates current. Check the Certificate status column on the vCenters page regularly. Renew Expiring certificates as soon as possible to prevent interruptions to data collection. An Expired certificate stops data flow from that vCenter until the certificate is renewed and the connection is refreshed.

Use filters effectively. When troubleshooting, apply a vCenter or time-period filter to narrow your focus before drilling into individual host or VM detail views.

Support

If you encounter an issue, contact your Omnissa representative or submit a support request through the standard Omnissa support portal. When filing a support request, include:

• The vCenter version and build number
• The Horizon version and build number
• The collector version
• A description of the affected monitoring surface (vCenter health, ESXi host, VM measures, or VM health)
• Any error messages or permission warnings visible in the Connection Health panel