fix(monitoring): make the reported key count self-describing instead of a bare number #109

Merged

abiba-bot merged 1 commits from fix/litellm-key-count-self-describing-20260916 into master

2026-09-16 15:35:36 +00:00

Author	SHA1	Message	Date
root	7f62f19c24	fix: litellm-key-count-self-describing-20260916 PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 6s Details PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 7s Details PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 6s Details PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 4s Details PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s Details The key-count line in litellm-health-check now reports self-describing output: '18 total (10 on page 1)' instead of bare '18' or '4'. Uses total_count from the paginated API response and names what was counted. Previous bare numbers could not reconcile changes between runs; now a reader sees both the total and the page 1 sample.	2026-09-16 15:20:50 +00:00