Skip to content

Omnissa Horizon · /// End-to-End Monitoring

Know your Horizon users are happy. Through the rebrand.

LoadGen runs the same scenario engine in continuous mode — synthetic Horizon sessions every minute, real-user DEM via SessionSight, and uptime checks across Connection Server, vCenter, and published apps. Omnissa-aware after the rebrand, VMware-Horizon-compatible before it.

See LoadGen on your Horizon stackTalk to an engineer

Synthetic + real-user DEMConnection Server-aware€899 / Agent / month

Live cockpit — KPI freshness, session health, time-range scrub.

The Problem

vCenter green. Horizon users angry.

Horizon monitoring is split across tools: Connection Server reports session state, vCenter reports infrastructure, your APM reports app health. None of them log in as an Omnissa user and click — which is where Horizon sessions actually break.

Three vendors, three blind spots.

Horizon Console shows Connection Server health. vCenter shows host health. APM shows app health. None of them run a synthetic Horizon user end-to-end with measured per-step latency.

Brand-transition fragmentation.

The VMware → Omnissa rebrand splits tooling and documentation across versions. Monitoring tools that depend on vendor APIs fall behind during the transition; LoadGen runs real user sessions, regardless of console branding.

No evidence-grade SLA proof.

Auditors want measured response times — not dashboard screenshots from three different consoles. Quarterly SLA reports become a manual reconciliation exercise.

Why LoadGen for Horizon monitoring

One timeline. Through the rebrand.

The same scenario that drives your Horizon load tests runs continuously as a synthetic user. SessionSight captures the real-user side. Uptime checks watch Connection Server and vCenter dependencies. One platform, one cockpit, one audit trail — regardless of VMware-vs-Omnissa branding.

Horizon-native synthetic users

Real Horizon sessions, real Connection Server auth, real published-app launches — fired every minute. Not HTTP samplers pretending to be Horizon clients.

SessionSight DEM on the same timeline

Heatmaps, replay, visitor journeys correlated against synthetic checks and infrastructure counters. One scrub bar across published apps and full desktops.

Evidence-grade SLA reporting

Every synthetic check, real-user session, and uptime event lands in queryable history. SLA reports generate on demand — for the auditor, not the spreadsheet sprint.

Guided setup

A Horizon monitoring profile, captured in 10 steps.

The same wizard that powers /products/monitoring. Connection Server captured once, replayed every synthetic check, every minute — across every region you deploy Core agents.

  • 10 named steps — Name · Target · Agents · Workload · Datasource · Schedule · SUT · Alerting · Summary.
  • Horizon target-environment selection inline — Connection Server URL, published-app vs full-desktop, agent strategy.
  • Same scenario captured here is reusable for load testing — one engine, two operational modes.
  • Synthetic sessions fire on schedule; results land in the live cockpit with connection-broker telemetry.

10-step monitoring profile wizard — autoplay, pause on hover.

Capability

What ships with End-to-End Monitoring for Horizon.

Continuous synthetic Horizon sessions

The same .lgs workload that drives Horizon load tests runs as a synthetic user — every minute, every region. Per-step latency, connection-broker round-trip, login time.

Learn more

SessionSight Digital Experience

Click heatmaps, scroll maps, rage-click detection, DOM-fidelity replay across desktop / tablet / mobile — filtered by country, browser, OS, device, UTM.

Learn more

Severity-aware alerting

Email, Webhook, SMS, WhatsApp — with maintenance windows and on-call routing. Alert on Connection Server health, vCenter binding, and Horizon session-density drift.

Learn more

Uptime + dependency tracking

HTTP, REST, SQL, and Azure / vCenter checks against Connection Server and Horizon dependencies. Incident management built in.

Learn more

Analytics & AI

AI-flagged connection-broker latency drift, published-app launch regressions, and anomaly scoring across every synthetic execution.

Learn more

LoadGen Insight + RBAC

Machine groups, data-health matrix, per-customer dashboards. Seven built-in roles plus custom permission trees — multi-tenant from day one.

Learn more

Real-user DEM

SessionSight catches what synthetic checks can’t.

Synthetic monitoring tells you the application responded. SessionSight tells you the Horizon user actually clicked. Heatmaps + rage-click detection on the same timeline as your synthetic Horizon probes.

  • Click, scroll, and rage-click heatmaps with intensity bands across desktop / tablet / mobile.
  • Desktop / tablet / mobile viewport switching with separate calibrated thresholds.
  • Deep-filter by country, browser, OS, device, UTM — production support workflow without a separate vendor.
  • Correlated against synthetic check + uptime events on a single scrub bar.

SessionSight heatmaps — click, scroll, rage-click modes.

Outcomes

What evidence-grade Horizon monitoring looks like.

Monitoring sessions captured

Before

—

After

250 M+

platform total
Platforms unified

Before

Multi-vendor

After

6 in one

one platform
Per-Agent / month

Before

Quote on req.

After

€899

transparent
Through the rebrand

Before

Brand-fragmented

After

Stack-honest

one engine

See it in action

Three Horizon monitoring surfaces on one platform.

Live cockpit

KPIs, sessions table, time-range scrub.

DEM heatmaps

Click, scroll, rage-click overlays.

Session replay

Image + DOM playback with event log.

What Horizon teams monitor with this

Three Horizon monitoring jobs.

SLA validation for Horizon

Generate evidence-grade SLA reports on demand. Per-region availability, per-app response time, p95 login latency — straight from the same data your alerts fire on.

See use case

Proactive UX detection

Catch Connection Server latency drift, published-app launch regression, and host-pool density issues before users open a ticket. Alert on the lead indicator.

See use case

Migration validation toward AVD

Some Horizon shops are evaluating AVD as part of vendor consolidation. LoadGen monitors both stacks on the same scenario shape — baseline Horizon, target AVD, on one timeline.

See use case

See Horizon monitoring on your own stack.

We’ll wire a synthetic Horizon user against your Connection Server URL, layer real-user DEM via SessionSight, and walk you through SLA reporting — on a call.

Request a Horizon monitoring demoSee Horizon platform overview

Questions

Frequently asked.

How does LoadGen handle the VMware Horizon → Omnissa Horizon brand transition?

LoadGen runs real Horizon sessions end-to-end — Connection Server, published apps, full desktops — regardless of whether the console says VMware or Omnissa. The synthetic monitoring is stack-honest about what the user actually experiences, not what the vendor API claims.

Does LoadGen support Horizon Connection Server clustering?

Yes — the synthetic Horizon user lands on whichever Connection Server the load balancer routes it to, exactly as a real user would. Per-step latency and login time are measured per-session, regardless of which broker in the cluster handled the connection.

Can LoadGen test Horizon published apps as well as full desktops?

Yes. The scenario engine handles both: full-desktop scenarios capture the connection-broker + Windows-session login path; published-app scenarios capture per-app launch and interaction. Both run on the same VDI agents.

How does monitoring correlate with vCenter / vSphere host counters?

SUT Monitoring binds vCenter and vSphere counters to every synthetic check — host CPU, memory, datastore latency, network throughput. Infrastructure health and measured user experience share one timeline.

What does Horizon monitoring cost?

€899 per Agent per month, with annual subscriptions including two months free. One Agent typically covers one Horizon farm or Connection Server cluster — scaling is per-environment.

How is this different from Omnissa Workspace ONE Assist or vRealize Operations?

Workspace ONE Assist focuses on remote support and device posture. vRealize Operations reports vSphere infrastructure health. LoadGen runs an actual Horizon user end-to-end every minute — measuring per-step latency, connection-broker round-trip, login time, and DEM behaviour. Different problem; complementary to existing Omnissa tooling.

LoadGen Official Logo