Base accepting the saturated full-r3 run on the user's 2026-10-31 host
warning rule instead of the swap decision and ask whether to re-shoot;
complete the report section with limits, metric freshness at 30 s and
per-class and per-component tables; correct derived numbers and the
quantile error wording; align H6 in design with the report; fix the
quantile_error docstring; park S1 and S4 as later proposals.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- [telemetry] trace_sample_ratio (ParentBased(TraceIdRatioBased), 1 keeps
ParentBased(ALWAYS_ON)) and metric_buckets (default|coarse with SLO bounds),
export interval <= 30 s; otel.sdk.span.started, span.live dropped; startup
records name ratio, buckets and interval
- bench: telemetry services on mtusi-bench, TELEMETRY=on switch for uploads
and queue, make bench_telemetry[_quick] with off/full/full-aa/head/tail/
metrics/balanced, rare events, lookup from Tempo/Loki/Prometheus, cost
sampler, verdicts H1-H8 and B1-B5; collector layers and lean Prometheus in
bench/otel with preflight checks
- REPORT: telemetry cost hypotheses and criteria before the label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>