Synthetic Monitoring · /// Cross-Vendor Platform
Synthetic checks that actually log in. Across every platform.
The same scenario engine that runs your load tests fires on a configurable schedule as a synthetic user across Citrix, AVD, 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 monitored environments.
The Problem
HTTP samplers say green. Users say no.
Many 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 general-purpose synthetic platforms focus on web and SaaS. EUC teams running Citrix, AVD, 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. 8 monitored environments. Real sessions.
The same `.lgs` scenario that drives your load tests fires as a synthetic user on a configurable schedule. Real Citrix session, real AVD session, real RDP connection, real OpenAPI flow. Captured once, replayed in both modes. LoadGen scales with available test infrastructure and agent capacity; 25,000+ users tested by LoadGen.
Real sessions, not probes
Synthetic Citrix users actually log in through StoreFront / Gateway / PNAgent / External Login and run multi-step interactions. AVD users run through a 7-step wizard with free-text Tenant / Client / Resource and a Classic/ARM checkbox. RDS uses an 8-step shared RDP/RDS wizard.
Same engine as load testing
The scenario authored in the 10-step monitoring profile wizard replays as synthetic monitoring AND as a load test. No re-authoring, no separate dashboard. One engine. Two operational modes.
Cross-vendor on one timeline
Citrix, AVD, Horizon, RDS, Web, and APIs across 8 monitored environments. Synthetic checks fire from the same Core agents and land in the same cockpit. One scrub bar, one root-cause path.
Schedules + maintenance windows
Synthetic checks fire on a configurable 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, and results sit side-by-side in the cockpit.
- Per-agent scheduling. Configurable cadence per persona.
- Maintenance windows applied automatically. Compliance-window exclusions tracked.
- Synthetic, uptime, and load-test data unified on the same timeline.
- Alerts route on per-step regression, not aggregate dashboard symptoms.
Synthetic check schedule. Per-agent, 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 on a configurable schedule across Citrix, AVD, Horizon, RDS, Web, and API. Monitoring runs on Core agents; load-test `.lgs` workloads run on Full agents. Playwright is supported on Core agents.
Learn more10-step monitoring profile wizard
Author a synthetic profile in 10 named steps. Same wizard model as load testing. Citrix wizard is 7 steps; AVD wizard is 7 steps; RDS wizard is 8 steps; SLO Setup Wizard is 5 steps; Uptime Check Wizard is 9 steps.
Learn moreSeverity-aware alerting
Alerting channels: Email, Webhook, SMS, WhatsApp, with maintenance windows and on-call routing. Alert on per-step regression, not aggregated dashboard symptoms.
Learn more20+ uptime check types
20+ check types running alongside synthetic users: Web/HTTP, DNS, network ports, mail/transport, certificate/security, and custom plugins, including Azure Function and Azure App Service uptime checks (real, as Uptime types, not AVD-coupled). 9-step Check Wizard. Incident lifecycle managed in the same platform.
Learn moreAnalytics & AI
AI-flagged anomalies and analytics reports across synthetic, load, and uptime data streams. Surfaces what changed across every release.
Learn moreService Levels orchestration
SLO types: Availability / Error rate / Transaction SLA. Error budgets, burn-rate alerts, and customer-facing public status pages on top of the same synthetic data stream. Audit-grade SLA evidence on demand.
Learn moreUptime and incident lifecycle
Synthetic checks plus 20+ uptime check types, one platform.
The same platform that fires synthetic users tracks dependency uptime across 20+ check types: Web/HTTP, DNS, network ports, mail/transport, certificate/security, and custom plugins. Azure Function and Azure App Service uptime checks are real (as Uptime types, not AVD-coupled). Incident lifecycle managed in the same UI.
- Web/HTTP, DNS, network ports, mail/transport, certificate/security, custom plugins.
- Azure Function and Azure App Service uptime checks shipped as Uptime types.
- Incident lifecycle: detect, escalate, resolve, post-mortem, all in one platform.
- Severity-aware routing to Email, Webhook, SMS, WhatsApp. Plain JSONL audit log with 30-day retention and purge.
Uptime incidents. Dependency checks and escalation timeline.
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
Where synthetic monitoring lives
Three synthetic monitoring jobs.
SLA validation across the estate
Generate evidence-grade SLA reports across Citrix, AVD, Horizon, RDS, and Web. Availability, per-app response time, and login p95 on demand via Service Levels (LG058 + LG059).
See use caseProactive regression detection
Catch per-step latency drift and login-time regression before users open a ticket. Alert on the lead indicator.
See use caseMulti-tenant synthetic monitoring
One platform, per-customer dashboards, and per-tenant RBAC (30 built-in roles plus custom roles, with OIDC SSO). 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, or Web environment, fire it on a configurable schedule from a Core agent, and walk you through the live cockpit on a call.
Questions
Frequently asked.
How is this different from general-purpose synthetic-monitoring platforms?
Most general-purpose synthetic-monitoring platforms focus on web and SaaS apps and use HTTP probes. LoadGen fires real sessions: actual Citrix users (via StoreFront / Gateway / PNAgent / External Login), AVD sessions (via the 7-step wizard with Classic/ARM checkbox), Horizon sessions, RDP connections, and OpenAPI flows. The synthetic check actually logs in and clicks, not 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, and results sit side-by-side in the cockpit. LoadGen scales with available test infrastructure and agent capacity.
Does Uptime cover Azure dependencies?
Yes. Azure Function and Azure App Service uptime checks ship as Uptime types, not AVD-coupled. They sit alongside the broader 20+ check types: Web/HTTP, DNS, network ports, mail/transport, certificate/security, and custom plugins.
What does synthetic monitoring cost?
€899 per Agent per month, with annual subscriptions including two months free. One Agent typically covers one environment. Scaling is per-environment.
How does alerting work?
Severity-aware alerting routes to Email, Webhook, SMS, and 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. Availability, Error rate, and Transaction SLA via the 5-step SLO Setup Wizard. Customer-facing public status pages ship in LG059. Availability and login p95 evidence exports to PDF or JSON for audit-grade responses.
