Skip to content
Service Levels · /// SLO / SLA / Status Pages

Service Levels — Promise What You Can Prove

SLO and SLA management on top of your Uptime, Monitoring, and Load Testing data. Normalize signals from every source, track error budgets, alert on burn rate, and publish a customer-facing status page from the same numbers your auditor sees.

Service Levels · Health · Checkout API
Mode: BasicOnline
A

Compliance — last 30 days

Rolling window · target 99.9% · 5-min buckets

Compliance

99.84%

target 99.9%

Good buckets

8,124

rolling 30 days

Effective

8,140

counted toward SLO

NoData

4

treated as failure

Compliance — rolling 30 days

Currently 0.06% below the 99.9% target.

Live
day -30day -20day -10now

Violations — last 30 days

4 ranges
TypeObjectiveReasonRange (UTC)Compliance
BreachCheckout API · AvailabilityHTTP 503 burst — 11 buckets2026-05-29 02:00 → 02:55 UTC99.84%
NoDataCheckout API · Availability3 consecutive NoData buckets2026-05-29 08:30 → 08:45 UTC
BreachPayments · Latency p95p95 > 800ms for 6 buckets2026-05-28 19:10 → 19:40 UTC99.71%
NoDataAuth · AvailabilitySource interval misaligned2026-05-28 11:00 → 11:15 UTC
© 2026 LoadGen. All rights reserved.
DocumentationSupportCreate Ticket

One Number · One Source of Truth

Cross-Source SLI Normalization — Uptime + Monitoring + Load Testing.

Every objective points at one source: an Uptime check, a Monitoring profile / datasource / measurement, or a Load Testing datasource. The Service Levels evaluator turns each one into the same shape — Good count, Effective count, NoData count, bucket-aligned. That’s how the same “Checkout availability ≥ 99.9%” number is comparable whether the signal is an HTTP probe, a synthetic Citrix session, or a load test pass rate.

Three source families
Uptime checks · Monitoring measurements · Load Testing datasources
NoData is a first-class state
Treat it as failure (default) or carve it out per objective.
Bucket-alignment warning
Flagged during setup when the bucket size doesn’t divide the source interval.
One number, every audience
The same 99.9% target backs Health, Violations, the public status page, and the audit ledger.

Live simulation · /config/service-levels/objectives

Guided Setup

5-Step SLO Setup Wizard.

Service, Objective, Source, Window, Review. Every field has a “what is this?” help card on the right. Bucket-alignment warnings fire client-side before the backend rejects you.

Service

Name, environment, timezone, owner, tier, sensitivity.

Live simulation · /config/service-levels/setup

Error Budgets & Burn-Rate Alerts

Budget — How Much Failure Can You Still Afford?

For every objective, the platform tracks how much of the error budget has been spent in the current window, and how fast you’re spending it.

Per-objective budget view
Budget total, consumed, remaining (% of total), and burn rate per hour.
Alert rules
Fire on Breached, NoData failure, or At risk (high budget burn) — each with a configurable severity.
Alert events feed
Every fire — with bucket-start and created-at timestamps for audit.
Business hours & exclusions
Maintenance windows and incidents don’t count against the budget.

Live simulation · /service-levels/operations

Health · Violations · Latest Snapshot

Compliance at a glance, violations you can drill.

One window selector drives the dashboard at /service-levels/health and the audit ranges at /service-levels/violations.

Health
Per-service rolling window (1–365 days). Per-objective Good / Effective / NoData counts. Latest active snapshot rows, and on-demand “Evaluate now”.
Violations
Breach and NoData ranges side by side — objective, source, reason, bucket span, and compliance % per range. Same window selector as Health.

Live simulation · /service-levels/health

Live simulation · /config/service-levels/objectives

Audit-Grade History

Every Change Tracked. Every Number Reproducible.

Version ledger with checksum chain
Every objective edit creates a new version with effective-from / effective-to UTC timestamps.
Recalculation jobs
Replay any historical window with the definitions that were active at the time. The API enforces one active recalc at a time so the audit trail stays clean.
JSON / CSV exports of snapshots and violations
For auditors, board reports, and whatever spreadsheet legal sends back.

Access Control · Sensitivity Masking

Show Customers What They Need. Hide What They Don’t.

Per-service ACL
Allow / deny principal lists per service.
Mask sensitive fields
A per-ACL toggle that hides sensitive fields from principals who aren’t on the allow list.
Tenant-scoped reads and writes
Definitions carry an optional tenant id. The API honours an X-Tenant-Id header — one appliance can scope services and snapshots per tenant.

Live simulation · /service-levels/acl

Live simulation · /status-pages/{slug}

Public Status Pages · LG059

A Customer-Facing Status Page From the Same Numbers Your Auditor Sees.

The same Service Levels snapshots that drive your internal Health view drive a public, anonymously-served page at /status-pages/{slug}. No second data pipeline. No reconciliation. One source of truth.

Per-page slug
customer-portal, b2b-api, anything URL-safe.
Published or Draft
Drafts stay operator-only; published pages render without authentication.
Pick which services appear
One page per audience — every page a curated subset.
Title is customer-facing copy
No internal naming leaks.
Operator-served, anonymously delivered
Served by the platform/appliance at /status-pages/{slug} — confirm with engineering that public rendering is enabled in your target build.

Scheduler · Storage

Operator controls — evaluation cadence, storage backend, schema provisioning.

Scheduler
Enabled / disabled state, evaluation interval and lookback window (minutes), max services per run, next-run and last-run details, plus an on-demand all-services evaluation cycle.
Storage
Authoritative snapshot store — SQL Server or PostgreSQL. Test connection and provision schema from the UI. Managed appliance ships PostgreSQL pre-configured, no DBA required.

Live simulation · /config/service-levels/storage

Pricing

Part of LoadGen Platform.

Service Levels (LG058) and Public Status Pages (LG059) are licensed modules. A trial may be available when you start. Check licensing for your deployment.

See Your First SLO Live in Five Minutes.

SLO and SLA management on top of your Uptime, Monitoring, and Load Testing data. Error budgets, burn-rate alerts, audit-grade history, and customer-facing status pages — all on the same numbers.

LoadGen Official Logo