Skip to content

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

Know your Horizon users are happy. Through the rebrand.

The same scenario engine and agent fleet that run Citrix and AVD monitoring run against Omnissa Horizon environments. Synthetic Horizon sessions on a configurable schedule, real-user DEM via SessionSight, and uptime checks across the dependencies you care about. Omnissa-aware after the rebrand, Horizon-compatible before it.

Synthetic + real-user DEMSame engine as Citrix and AVD monitoring€899 / Agent / month

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

The Problem

Infrastructure green. Horizon users angry.

Horizon monitoring is split across tools. Infrastructure reports host health, app performance reports app health, none of them log in as a user and click, which is where Horizon sessions actually break.

Multiple consoles, multiple blind spots.

Several consoles each report a slice of the stack. None of them run a synthetic Horizon user end-to-end with measured per-step latency.

Brand-transition fragmentation.

The VMware to Omnissa rebrand splits tooling and documentation across versions. LoadGen runs real Horizon sessions regardless of console branding.

No evidence-grade SLA proof.

Auditors want measured response times, not dashboard screenshots from multiple consoles. Quarterly SLA reports become a manual reconciliation exercise.

Why LoadGen for Horizon monitoring

One timeline. Through the rebrand.

The same scenario engine and Core / Full / VDI agents that drive Citrix and AVD monitoring run against Omnissa Horizon. SessionSight captures the real-user side. Uptime checks watch the dependencies you nominate. One platform, one cockpit, one audit log, regardless of VMware-vs-Omnissa branding.

Synthetic Horizon sessions

Real Horizon sessions fired on a configurable schedule by the same scenario engine that drives Citrix and AVD. Not HTTP samplers pretending to be Horizon clients.

SessionSight DEM on the same timeline

Click and scroll heatmaps, DOM-fidelity replay, journey analysis, and visitor tracking, correlated against synthetic checks on one scrub bar. Capture-time DOM masking (Strict / Balanced / Relaxed) keeps the privacy review survivable.

Evidence-grade SLA reporting

Every synthetic check, real-user session, and uptime event lands in queryable history. Service Levels (LG058 + LG059) generates audit-grade SLA reports on demand, not in the spreadsheet sprint.

Guided setup

A Horizon monitoring profile, captured in 10 steps.

The same 10-step monitoring profile wizard used for Citrix and AVD also captures Horizon scenarios. Same scenario captured here is reusable for load testing through the Load & Performance Testing module, load-test Horizon at concurrency through the same scenario engine.

  • 10 named steps. Same wizard as Citrix and AVD monitoring profiles.
  • Same scenario captured here is reusable for load testing. One engine, two operational modes.
  • Load-test Horizon at concurrency through the same scenario engine via Load & Performance Testing.
  • Synthetic sessions fire on a configurable schedule. Results land in the live cockpit.

10-step monitoring profile wizard. Autoplay, pause on hover.

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. Click and scroll heatmaps on the same timeline as your synthetic Horizon probes.

  • Click and scroll heatmaps with intensity bands across desktop, tablet, and mobile.
  • Two replay modes (screenshot slideshow OR DOM reconstruction) with a fixed 8-value speed dropdown from 0.25× to 12×.
  • Deep-filter by country, browser, OS, device, and UTM. Journey analysis and visitor tracking ship in the same surface.
  • Correlated against synthetic checks and uptime events on a single scrub bar.

SessionSight heatmaps. Click and scroll modes.

Proof

Numbers from the platform.

250M+

Monitoring sessions

across the customer base

8

Products, one platform

testing + monitoring + analytics + service levels

6

Platforms covered

Citrix · AVD · Horizon · RDS · Web · FAT

From €899

Per Agent / month

published, predictable pricing

See it in action

Three Horizon monitoring surfaces on one platform.

Live cockpit

KPIs, sessions table, time-range scrub.

DEM heatmaps

Click and scroll overlays.

Session replay

Screenshot slideshow or DOM reconstruction.

See Horizon monitoring on your own stack.

We’ll wire a synthetic Horizon user against your environment, layer real-user DEM via SessionSight with capture-time DOM masking, and walk you through SLA reporting on a call.

Questions

Frequently asked.

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

LoadGen runs real Horizon sessions end-to-end regardless of whether the console says VMware or Omnissa. The synthetic monitoring is stack-honest about what the user actually experiences. There is no Horizon-dedicated wizard and no native vCenter integration, the same scenario engine that runs Citrix and AVD also runs Horizon scenarios.

Can LoadGen load-test Horizon at concurrency?

Yes. LoadGen can load-test Horizon at concurrency through the same scenario engine, the same Core / Full / VDI agent fleet used for Citrix and AVD. Synthetic monitoring on a configurable schedule replays the same scenario for continuous coverage.

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

Yes. The scenario engine handles both: full-desktop scenarios and published-app scenarios. Both run on the same agent fleet, load-test `.lgs` workloads on Full agents, monitoring on Core agents.

How does monitoring correlate with infrastructure counters?

SUT Monitoring binds generic Windows perfmon counters to every synthetic check. Infrastructure counter binding follows the configured SUT scope. Native vCenter integration is not part of the platform; positioning is around the synthetic user signal and its correlation with the counters you nominate.

What does Horizon monitoring cost?

€899 per Agent per month for End-to-End Monitoring, with annual subscriptions including two months free. Scaling is per-environment.

How is this different from other EUC monitoring tools?

LoadGen runs an actual Horizon user end-to-end on a configurable schedule, measuring per-step latency, login time, and DEM behaviour. The same scenario engine also drives load tests, load-test Horizon at concurrency through the same scenario engine. Different problem; complementary to existing Omnissa tooling.

LoadGen Official Logo