Synthetic Monitoring · /// Cross-Vendor Platform
Synthetic checks that actually log in. Across every platform.
The same scenario engine that runs your load tests fires every minute as a synthetic user — across Citrix HDX, AVD ARM, Horizon, RDS, Web, and APIs. Real auth flows, real sessions, real per-step latency. Not HTTP samplers pretending to be users.
Citrix · AVD · Horizon · RDS · Web · APIReal sessions, not HTTP samplers€899 / Agent / month
Live cockpit — synthetic check freshness across 6 platforms.
The Problem
HTTP samplers say green. Users say no.
Most synthetic-monitoring tools fire HTTP probes and call it monitoring. A 200 OK on StoreFront is not a working Citrix session. A 200 OK on the AVD broker is not a launched AVD desktop. The gap is where production incidents live.
Probes vs sessions.
HTTP probes hit endpoints. Real users open sessions. The difference: auth flows, protocol negotiation, app launches, per-step interactions. Probes don’t see any of it.
Web-only synthetic monitoring.
Most synthetic platforms (Datadog, Pingdom, Catchpoint) focus on web / SaaS. EUC teams running Citrix HDX, AVD ARM, or Horizon need synthetic users that speak the protocols.
No reuse from load tests.
Two separate tools means two scenario authoring efforts, two definitions of "working", two dashboards. The scenario you tested under load is not the one your synthetic monitor fires.
Why LoadGen for synthetic monitoring
One scenario engine. Six platforms. Real sessions.
The same .lgs scenario that drives your load tests fires as a synthetic user every minute. Real HDX session, real AVD ARM-discovered desktop, real RDP connection, real OpenAPI flow. Captured once, replayed in both modes.
Real sessions, not probes
Synthetic Citrix users actually log in through StoreFront, launch HDX sessions, and execute multi-step interactions. AVD users run ARM-discovered AVD sessions with FSLogix profile loads measured.
Same engine as load testing
The scenario authored in the wizard for load testing replays as synthetic monitoring — no re-authoring, no separate dashboard. One engine, two operational modes.
Cross-vendor on one timeline
Citrix HDX, AVD ARM, Horizon, RDS, Web, and APIs — synthetic checks fire from the same Core agents and land in the same cockpit. One scrub bar, one root-cause path.
Schedule + multi-region
Synthetic checks fire on schedule. From every region.
Core agents deploy on-prem, in cloud, or in remote-office locations. The same .lgs scenario fires from every agent on schedule; per-region results visible side-by-side in the cockpit.
- Per-agent / per-region scheduling — every minute, every persona, every region.
- Maintenance windows applied automatically; compliance-window exclusions tracked.
- Synthetic + uptime + load-test data unified on the same timeline.
- Alerts route on per-region per-step regression, not aggregate dashboard symptoms.
Synthetic check schedule — per-agent, per-region, per-persona.
Capability
What ships with the synthetic monitoring platform.
Continuous synthetic sessions
The same .lgs workload that drives load tests fires as a synthetic user every minute — across Citrix, AVD, Horizon, RDS, Web, API. Per-step latency, p95 by protocol.
Learn more10-step monitoring wizard
Author a synthetic profile in 10 named steps — Target, Agents, Workload, Datasource, Schedule, SUT, Alerting, Summary. Same wizard model as load testing.
Learn moreSeverity-aware alerting
Email, Webhook, SMS, WhatsApp — with maintenance windows and on-call routing. Alert on per-step regression, not aggregated dashboard symptoms.
Learn moreUptime + incident management
HTTP, REST, SQL, Azure Function, Azure App Service checks running alongside synthetic users. Incident lifecycle managed in the same platform.
Learn moreAnalytics & AI
AI-flagged latency drift, login-time regressions, anomaly scoring per synthetic execution. Surfaces what changed across every release.
Learn moreService Levels orchestration
SLO definitions per-region, per-app, per-platform on top of the same synthetic data stream. Audit-grade SLA evidence on demand.
Learn moreUptime + incident lifecycle
Synthetic checks + uptime, one platform.
The same platform that fires synthetic users tracks dependency uptime — HTTP, REST, SQL, Azure Function, Azure App Service. Incident lifecycle managed in the same UI.
- HTTP / REST / SQL / Azure dependency checks alongside synthetic users.
- Incident lifecycle: detect → escalate → resolve → post-mortem in one platform.
- Severity-aware routing: Email / Webhook / SMS / WhatsApp.
- Audit trail captures every check, every escalation, every resolution.
Uptime incidents — dependency checks + escalation timeline.
Outcomes
What real synthetic monitoring looks like.
Before
—
After
250 M+
Before
Web only
After
6 platforms
Before
Re-authored
After
Captured once
Before
Quote on req.
After
€899
Where synthetic monitoring lives
Three synthetic monitoring jobs.
SLA validation across the estate
Generate evidence-grade SLA reports across Citrix + AVD + Horizon + RDS + Web. Per-region availability, per-app response time, p95 login latency on demand.
See use caseProactive regression detection
Catch per-step latency drift, login-time regression, and protocol-channel pressure before users open a ticket. Alert on the lead indicator.
See use caseMulti-tenant synthetic monitoring
One platform, per-customer dashboards, per-tenant RBAC. The shape MSPs use to deliver Synthetic-Monitoring-as-a-Service.
See use caseSee cross-vendor synthetic monitoring on your stack.
We’ll wire a synthetic user against your Citrix / AVD / Horizon / RDS / Web environment, fire it every minute from a Core agent, and walk you through the live cockpit — on a call.
Questions
Frequently asked.
How is this different from Datadog / Pingdom / Catchpoint?
Most synthetic-monitoring platforms focus on web / SaaS apps and use HTTP probes. LoadGen fires real sessions — actual HDX users, ARM-discovered AVD desktops, Horizon Connection Server logins, RDP connections — across 6 platforms. The synthetic check actually logs in and clicks; it isn’t a 200-OK heartbeat.
Does the synthetic check reuse my load-test scenarios?
Yes — that’s the primary design choice. The same .lgs scenario authored in the wizard for load testing replays as a synthetic monitoring check. Author once, run as load AND as continuous monitoring. No separate scenario library.
Can synthetic checks fire from multiple regions?
Yes. Core agents deploy on-prem, in cloud, or in remote-office locations. The same scenario fires from every agent on schedule; per-region results visible side-by-side in the cockpit.
What does synthetic monitoring cost?
€899 per Agent per month, with annual subs including two months free. One Agent typically covers one environment — scaling is per-environment, not per-user.
How does alerting work?
Severity-aware alerting routes to Email / Webhook / SMS / WhatsApp with maintenance windows and on-call rotation. Tests can be muted explicitly during change windows; alerts can be debounced via consecutive-failure thresholds.
Can we generate SLA reports from synthetic data?
Yes — Service Levels (LG058 + LG059) orchestrates SLO definitions on top of the same synthetic data stream. Per-region availability, per-app response time, p95 login latency — exportable to PDF / JSON for audit-grade responses.
