Files
rippled/docs
Pratik Mankawde ea4282f6e0 docs(telemetry): correct the stale metric-gate counts in the runbook
The "What Gets Validated" table claimed "58 metrics in 23 categories". Both
numbers were stale: generalising required_labels and adding the asserted
io_latency group changed the gate to 66 checks across 24 asserting categories
(61 metric names plus 5 required_labels checks).

Derived from the inventory rather than counted by hand -- ran the validator's
own _metric_check_targets() against expected_metrics.json:
  metric names = 61 | label checks = 5 | TOTAL = 66
  asserting groups = 24
  label checks per group = {'spanmetrics': 4, 'job_queue': 1}

Also records that labels are gated at all. They were declared in the contract
but nothing read the key until the check was generalised, so four spanmetrics
labels were documented as required while going unverified -- the table
described existence checks only and gave no hint that a label regression was
now catchable.

The other rows in the same table were re-derived and are still accurate:
spans 41 total / 26 required / 15 optional, parity 6 span attributes + 4 value
bounds = 10, dashboards 15 uids against 15 provisioned files, logs 2.
2026-08-24 20:50:34 +01:00
..
2020-03-30 18:57:35 -04:00