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. Per-region availability, per-app response time, 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 — per-region availability + p95 + 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, ControlUp — each reports 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 per-region per-minute 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 every minute 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 + LG059 — SLO definition, threshold orchestration, compliance-window management. Built on the same Monitoring engine; no separate SLA tool license.
Per-minute measured evidence
Every synthetic check, real-user session, and uptime event captured. Per-region per-minute availability. Auditors see the raw data, not aggregated screenshots.
Cross-stack on one timeline
Citrix HDX, AVD ARM, Horizon connection-broker, 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-region. 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-region per-minute availability data, exportable to PDF / JSON.
- Per-app response time, p95 login latency, 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 — per-region availability + p95.
Capability
What ships with the SLA monitoring platform.
SLO orchestration (LG058 + LG059)
Define SLOs per-region, per-app, 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 every minute — Citrix HDX, AVD ARM, Horizon, RDS. Per-step latency, p95, availability.
Learn moreEvidence-grade reporting
Per-region per-minute availability. Per-app response time. p95 login latency. Maintenance windows applied automatically. Audit pack exports to PDF / JSON.
Learn moreSLO-breach alerting
Severity-aware alerting on SLO breach — Email, Webhook, SMS, 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
Seven 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 + SLA evidence.
- Captured once, replayed across modes — Citrix HDX, AVD ARM, Horizon, RDS.
- Synthetic checks fire every minute; 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-region 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 + 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, 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 / 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 per-region per-app, apply compliance windows automatically, 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-region per-minute availability data, per-app response time, p95 login latency — captured in queryable history. Maintenance windows applied automatically. Audit pack exports to PDF / 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 (7 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.
