Service Levels · /// SLA Monitoring Platform
SLA evidence on demand. Not a quarterly spreadsheet sprint.
The Service Levels module (LG058 + LG059) ships SLO orchestration on top of the same scenario engine that runs your load tests and monitoring. Availability, per-app response time, and p95 login latency generated for auditors on demand. Across Citrix, AVD, Horizon, and RDS.
Audit-ready SLA reportsCross-stack (Citrix · AVD · Horizon · RDS)Service Levels module, included
SLA evidence pack. Availability, p95, and compliance window.
The Problem
Auditors want measured numbers. Dashboards lie.
Most VDI estates report SLA compliance via quarterly hand-curated screenshots stitched from three monitoring tools. The numbers might be defensible. Or might not. The audit either way is a multi-week exercise.
Three vendors, three definitions.
Citrix Director, Azure Monitor, and ControlUp each report a slightly different definition of "available". Quarterly SLA reports become a manual reconciliation across formats.
Screenshots don’t survive audit.
A dashboard screenshot is not measured evidence. Auditors want availability with timestamped session-level data, not aggregated quarterly summaries.
Compliance windows hand-curated.
Maintenance windows, planned downtime, and excluded intervals applied by hand in spreadsheets. Errors compound. Defending the number in front of an auditor takes hours.
Why LoadGen for SLA monitoring
Same engine. One audit trail.
The .lgs scenario that runs as a synthetic user on a configurable schedule is also the SLA evidence source. Service Levels orchestrates the SLO definitions. The underlying data is the same continuous monitoring stream. One audit trail, one source of truth.
Service Levels module included
LG058 and LG059 ship SLO definition, threshold orchestration, and compliance-window management. Built on the same Monitoring engine. No separate SLA tool license.
Measured evidence on a configurable cadence
Every synthetic check, real-user session, and uptime event captured. Per-check availability. Auditors see the raw data, not aggregated screenshots.
Cross-stack on one timeline
Citrix HDX, AVD, Horizon, and RDS all unified. One SLO definition can span multiple stacks. One audit pack covers the whole VDI estate.
Audit-ready evidence
Per-minute availability. Per-app.
The Service Levels module surfaces SLA evidence as raw measured data, not as a hand-curated quarterly screenshot. Compliance windows applied automatically. Maintenance exclusions tracked in the same UI.
- Per-minute availability data, exportable to PDF or JSON.
- Per-app response time, p95 login latency, and maintenance-window exclusions.
- Compliance windows applied automatically. No manual reconciliation.
- The same data your alerts fire on is the same data auditors see.
SLA evidence pack. Availability and p95.
Capability
What ships with the SLA monitoring platform.
SLO orchestration (LG058 + LG059)
Define SLOs per app, and per platform. Threshold orchestration tracks compliance windows, planned-maintenance exclusions, and severity escalation.
Learn moreContinuous synthetic monitoring
The same scenario engine that runs your load tests fires as a synthetic user on a configurable schedule across Citrix HDX, AVD, Horizon, and RDS. Per-step latency, p95, availability.
Learn moreEvidence-grade reporting
Per-minute availability. Per-app response time. p95 login latency. Maintenance windows applied automatically. Audit pack exports to PDF or JSON.
Learn moreSLO-breach alerting
Severity-aware alerting on SLO breach to Email, Webhook, SMS, and WhatsApp. Lead-indicator alerts before the compliance window closes.
Learn moreAnalytics & AI for root cause
AI-flagged regression scoring across every synthetic execution. When an SLO breaches, the platform surfaces what changed. Not a 50-page incident review.
Learn moreRBAC + per-tenant audit trail
multiple built-in roles plus custom permission trees. Per-customer audit trails for MSPs delivering Monitoring-as-a-Service.
Learn moreSame engine, monitoring mode
The scenario behind the SLO is the same one in load tests.
Author once. Replay as load test for capacity sign-off. Replay as continuous synthetic monitoring for SLA evidence. No separate SLA tool, no separate data silo.
- Same .lgs scenario drives load, monitoring, and SLA evidence.
- Captured once, replayed across modes: Citrix HDX, AVD ARM, Horizon, and RDS.
- Synthetic checks fire on a configurable schedule. Results land in the same cockpit.
- Service Levels orchestration sits on top of the live monitoring data, not a separate tool.
Live cockpit. Same data drives SLO orchestration.
Outcomes
What evidence-grade SLA monitoring looks like.
Before
Quarterly sprint
After
On demand
Before
Screenshots
After
Measured
Before
Multi-tool
After
6 platforms
Before
Hand-rolled
After
LG058+LG059
Where SLA monitoring lives
Three SLA jobs the platform actually does.
Compliance-driven enterprise SLA
Per-app availability evidence for audit teams in regulated industries. Same data, every quarter, no reconciliation sprint.
See use caseSLO orchestration across VDI estate
Define SLOs once, apply across Citrix, AVD, Horizon, and RDS. Threshold orchestration tracks compliance windows automatically.
See use caseMSP per-tenant SLA reporting
Multi-tenant from day one. Per-customer SLA packs, per-tenant RBAC, and per-account audit trails. The shape MSPs use to deliver Monitoring-as-a-Service.
See use caseSee SLA evidence on your own VDI estate.
We’ll wire a synthetic user against your Citrix, AVD, Horizon, or RDS, define an SLO via Service Levels, and generate a sample evidence pack on a call.
Questions
Frequently asked.
How is Service Levels different from a standard monitoring report?
Standard monitoring reports surface dashboards and alerts. Service Levels (LG058 + LG059) ships SLO orchestration. Define thresholds, apply compliance windows automatically, and generate audit-grade evidence packs on demand. The data source is the same Monitoring engine. The orchestration layer is what changes.
Does this work across Citrix, AVD, Horizon, and RDS?
Yes. The Service Levels orchestration layer sits on top of the unified Monitoring engine, which covers all 6 platforms (Citrix, AVD, Horizon, RDS, Web, FAT). One SLO definition can span multiple stacks. One audit pack covers the whole estate.
What evidence do we hand to an auditor?
Per-minute availability data, per-app response time, and p95 login latency, captured in queryable history. Maintenance windows applied automatically. Audit pack exports to PDF or JSON. Auditors see the same data your alerts fired on.
How does compliance-window exclusion work?
Maintenance windows are defined per environment in the Service Levels module. When a window is open, synthetic checks continue firing but the SLA calculation excludes them automatically. No manual reconciliation, no spreadsheet exception lists.
What does SLA monitoring cost?
End-to-End Monitoring is €899 per Agent per month with annual subs including two months free. The Service Levels module (LG058 + LG059) is included with Monitoring tier subscriptions. See the pricing page for multi-module bundle details.
Can multiple tenants share one SLA monitoring deployment?
Yes. LoadGen Insight ships per-tenant RBAC (multiple built-in roles plus custom permission trees), per-customer dashboards, and per-account audit trails. The multi-tenant shape MSPs use to deliver SLA-as-a-Service to a customer book.
