Description
WaitDuration exists per request in internal/tsapi/transport.go but no utilization/queue-depth gauge tells an MSP which tailnet is closest to saturating the shared Tailscale API quota before requests visibly queue. Export a per-tailnet utilization or wait-time signal, catalogue it, and surface it on the health dashboard API panel.
Acceptance Criteria
- #1 A per-tailnet gauge/histogram exposes rate-limit pressure before saturation
- #2 Catalogued and visualized on the health dashboard
Definition of Done
- #1 just check passes (the full gate; it is what CI enforces)
- #2 just gen leaves no diff (only if a generated artifact’s inputs changed)
- #3 just –fmt –check passes and every new recipe has a # doc comment and a [group(…)]
Implementation Plan
Lane D implements per-tailnet API rate-limit utilization from transport response state, with cardinality-bounded telemetry and an assigned-tab panel.
Final Summary
Added the per-tailnet API rate-limit utilization gauge, catalog and semantic attribute coverage, and a health-dashboard panel for pressure before saturation. Implementation SHA f35b6ab. Final integrated just check passed at 5b55617; exact-head CI run 33354208183 completed success.