slo definition audit derived

{
  "input": {
    "body": {
      "objective": "99.99",
      "window_days": 30,
      "burn_rate_alerts": [
        {
          "name": "slow burn",
          "burn_rate": 1.5,
          "window_hours": 720
        }
      ],
      "expected_events_per_day": 1000
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "limits": {
        "maxLines": 20000,
        "maxSpans": 10000,
        "maxFields": 500,
        "maxSamples": 20000,
        "maxFindings": 500,
        "maxJsonBytes": 2097152
      },
      "passed": false,
      "complete": true,
      "findings": [
        {
          "code": "BUDGET_IS_FEWER_THAN_TEN_EVENTS",
          "detail": "The budget for this window is 3 failed event(s). Below about ten the measurement is dominated by chance rather than by service quality, so the objective will look noisy however the service behaves."
        },
        {
          "code": "BURN_ALERT_FIRES_AFTER_EXHAUSTION",
          "alert": "slow burn",
          "detail": "slow burn watches a 720-hour window for a burn rate of 1.5, which exhausts the whole budget in 480.0 hours. The alert cannot fire before the budget is gone."
        },
        {
          "code": "ONLY_ONE_BURN_ALERT",
          "detail": "One burn-rate alert cannot be both fast on a severe burn and quiet on a slow one. Two or more windows at different rates is what makes a burn alert usable."
        }
      ],
      "measurable": false,
      "request_id": "example-request",
      "service_id": "slo_definition_audit",
      "assumptions": [
        "Everything is computed with exact decimals rather than floating point. An error budget is a small difference between two numbers close to one, which is precisely where binary floating point loses the ...",
        "The central check is observability rather than ambition: with a thousand events in the window, one failure is already a tenth of a percent, so an objective of 99.99% is met with zero failures and brea...",
        "A single burn-rate alert is reported because one window cannot be both fast on a severe burn and quiet on a slow one. Two or more at different rates is what makes the alert usable."
      ],
      "limitations": [
        "The definition supplied. Whether the objective matches what users need, and whether the chosen indicator reflects their experience, are outside this.",
        "measurable is true only when the objective can be observed at the volume supplied and every burn alert would fire usefully. Not a judgement that the objective is right."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "window_days": 30,
      "not_examined": [],
      "finding_count": 3,
      "budget_fraction": "0.000100000",
      "service_version": "1.0.0",
      "burn_rate_alerts": [
        {
          "name": "slow burn",
          "burn_rate": 1.5,
          "window_hours": 720,
          "budget_consumed_when_firing": 1.5,
          "hours_to_exhaust_at_this_rate": 480
        }
      ],
      "findings_by_code": {
        "ONLY_ONE_BURN_ALERT": 1,
        "BUDGET_IS_FEWER_THAN_TEN_EVENTS": 1,
        "BURN_ALERT_FIRES_AFTER_EXHAUSTION": 1
      },
      "objective_percent": "99.990000",
      "allowed_bad_minutes": 4,
      "allowed_failed_events": 3,
      "expected_events_in_window": 30000
    }
  }
}