| Omnissa Monitor 2609 | 01 OCT 2026 |
Omnissa Monitor 2609
Omnissa Monitor is an on-premises monitoring and observability solution for Omnissa Horizon 8 virtual desktop infrastructure. It gives administrators and operations teams visibility across the Horizon 8 stack, from infrastructure components through to end-user experience in a single console.
This is the initial release.
Key capabilities
- Single pane of glass: Monitor Horizon Connection Servers, Unified Access Gateways (UAGs), and end-user sessions from one console.
- End-user experience metrics: Track logon duration, protocol latency, packet loss, and CPU and memory utilization.
- Infrastructure health: Monitor Connection Server and UAG health, certificate expiry, and session utilization.
- vSphere observability: Monitor the underlying vSphere clusters, ESXi hosts, and virtual machines supporting your Horizon environment.
- Historical analysis: Analyze trends and troubleshoot past issues using retained historical data.
- Databricks integration: Stream Horizon 8 infrastructure and session metrics to a Databricks lakehouse for analytics and long-term storage.
Feature tiers
| Tier | Entitlement |
|---|---|
| Standard (Basic mode) | Bundled with a valid Horizon Term license |
Omnissa Monitor Advanced, which enables Digital Experience (DEX) features, is not supported in this release.
Compatibility
Supported data sources
Omnissa Monitor collects data from the following sources:
| Data source | Monitored components |
|---|---|
| Horizon Connection Server | Connection Server cluster health, session data, pod status |
| Unified Access Gateway | UAG health, certificate expiry, session utilization, CPU and memory |
| Horizon Agent (VDI VMs) | CPU, memory, protocol latency, packet loss, logon duration |
| vCenter Server | Clusters, ESXi hosts, virtual machines, datastores |
For supported versions of each component, see the Omnissa Interoperability Matrix.
Note: Horizon component versions and the Omnissa Monitor appliance build use separate version numbering. The appliance build for this release is 2609; the minimum supported Horizon component version is v2603.
Appliance requirements
| Resource | Minimum |
|---|---|
| CPU | 16 vCPUs |
| Memory | 40 GB RAM |
| Storage | 600 GB |
| Deployment format | OVA / OVF template |
| Network | Static IP, default gateway, netmask, and DNS configured |
Full prerequisites, including port and protocol requirements, are in the Omnissa Monitor Guide.
Known limitations
- High availability is not supported. This release supports a single-appliance deployment only.
- Cloud Pod Architecture (CPA) deployments are not supported. Omnissa Monitor 2609 requires on-premises vCenter/vSphere deployment.
- Horizon 8 pods with a configured Horizon Edge Gateway are not supported. These pods cannot be onboarded to Omnissa Monitor.
Known issues
- Private NSX-T segments must use valid RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) for OVA deployments.
- When a pipeline is in a Running state and has an error count greater than zero, the errors may indicate a configuration issue or a temporary interruption in the data flow. For transient issues, processing may resume successfully during a subsequent data synchronization cycle. If errors do not clear or continue to increase, review the Databricks configuration and credentials.
- When adding a second co-located pod, the FQDN must include the required port. If the port is omitted, agent monitoring will not function and session data will not be displayed. To recover, the customer must delete the affected pod and recreate it with the correctly configured FQDN and port.
Resolved issues
Not applicable. This is the initial release.
Installation and upgrade
Omnissa Monitor is delivered as an OVA appliance for deployment on vCenter/vSphere. Download the OVA from Customer Connect.
Upgrade is not applicable for the initial release.
For deployment steps, see Deploying the Omnissa Monitor Appliance in the Omnissa Monitor Guide.
Support
Contact your Omnissa representative or submit a support request through the standard Omnissa support portal. When filing a request, include the vCenter version and build, the Horizon version and build, the collector version, a description of the affected monitoring surface, and any error messages visible in the Connection Health panel.
Documentation
For deployment, configuration, and troubleshooting, see the Omnissa Monitor Guide.
Localized Content for Omnissa Docs
For details on Omnissa's localization strategy, see KB article "Announcing Omnissa Localization Support".
Support Contact Information
Contact your Omnissa representative or submit a support request through the standard Omnissa support portal. When filing a request, include:
- The vCenter version and build
- The Horizon version and build
- The collector version
- A description of the affected monitoring surface
- Any error messages visible in the Connection Health panel
To learn about support policies, see Omnissa Customer Connect. For information on filing a support request in Customer Connect or via the Cloud Services Portal, see https://kb.omnissa.com/s/article/2006985.
Was deze pagina nuttig?