› Reliability command[01/05]

CUSTOMER RELIABILITY, NOT PLATFORM AVERAGES

Every promise.
Measured.

TrueSLA turns the SigNoz telemetry you already collect into a live, per-customer contract ledger, before hidden failures become financial liability.

WINDOW · -SOURCE · TRACES @ -%UPDATED · -
THE TRUTH GAPWAITING FOR TELEMETRY
Global availability-%● AWAITING SIGNOZ
→
Worst customer availability-%● AWAITING TENANT TRACES
Protected MRR—
Credit exposure—
Tenants observed-
› How TrueSLA works[02/05]

THE BLIND SPOT, MADE VISIBLE

One green average.
One customer on fire.

ILLUSTRATIVE EXAMPLE · LIVE NUMBERS ARE IN THE LEDGER BELOW

GLOBAL AVERAGE99.9%LOOKS HEALTHY
but
ACME REALITY97.9%CONTRACT BREACH

HOW TRUESLA WORKS

ONE AUTONOMOUS CONTROL LOOP · LIVE INSIDE SIGNOZ
  1. 01OBSERVE

    Tag every request

    Each OpenTelemetry request carries the customer identity: Acme, Globex, or whoever made it.

  2. 02INGEST

    Count it, unsampled

    Every request is counted before any sampling decision, so the SLI stays exact. Traces ride alongside to explain failures.

  3. 03DECIDE

    Measure each promise

    TrueSLA checks both halves of the contract per customer: did enough requests succeed, and were they fast enough.

  4. 04FORECAST

    Price the risk

    A breach opens, provisional credit exposure appears, and the Credit Clock estimates the next tier.

  5. 05ACT

    Page with proof

    A customer-scoped SigNoz alert fires with checksummed evidence, failed trace samples, and likely cause.

THE ONE-LINE VERSION

TrueSLA turns traces you already collect into per-customer SLA truth: who is failing, what is at risk, how fast it is getting worse, and the proof to act on it.

TRACES→CONTRACT→EXPOSURE→PROOF
› Customer truth ledger[03/05]

ACTUAL VS. PROMISED

The customer is
the unit of reliability.

Every customer here is discovered from live SigNoz traces, not a seed list. Contracted customers get SLA truth and credit exposure; newly seen ones surface as unprotected until you attach a contract.

Customer / contractLive request mixAvailabilityp95ExposureStateControl
Reading customer truth from SigNoz…
› Exposure & evidence[04/05]
CURRENT EXPOSURE
CONNECTING TO SIGNOZ

Building the
live ledger.

Waiting for the first customer-scoped telemetry window. No contract verdict has been issued yet.

CONTRACT-AS-CODE · CREDIT SCHEDULE

From reliability
to financial consequence.

Provisional exposure only. Contract exclusions and final eligibility remain reviewable.

Immutable archive off. Set an S3 Object Lock bucket and every evidence bundle is also written somewhere it cannot be altered or deleted, even by someone with database access here.

MEASURED, NOT ASSERTED

Is the money math
actually right?

Showing one breach proves nothing about the cases where TrueSLA must stay quiet. This replays a committed set of labelled windows through the same decision function the live ledger uses, including thin traffic that must not be billed and a breach that is genuinely owed nothing. It runs offline, with no SigNoz and no model.

Scoring the engine…

TRACE-LINKED BREACH HISTORY

Every claim has
receipts.

No breach evidence recorded yet. Inject a tenant-scoped fault to demonstrate the full loop.

› System provenance[05/05]