docs(proxy): document gateway request counts - #768
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
yassin-berriai
force-pushed
the
litellm_sgr_gateway_requests_docs
branch
from
August 5, 2026 17:55
e5b65a9 to
dc68a49
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR
Documents the gateway request counts that BerriAI/litellm#35717 adds
The Successful Requests and Failed Requests tiles on the Usage page, and the new Gateway Requests by Endpoint chart, are now counted by the proxy's request-metrics middleware at the ASGI edge instead of being derived from spend logs. That changes what the number means, and it deliberately does not tie out against the per-key and per-model breakdowns on the same page, so the difference is worth writing down rather than leaving people to discover it
Three pages change.
endpoint_activity.mdgets a "Gateway Request Counts" section covering what is counted, the flush behaviour, why the number disagrees with the spend rollups, and the/gateway/daily/activityendpoint with a curl and a response shape.cost_tracking.mdgets a note on/user/daily/activitypointing at the new endpoint for callers who want gateway counts.db_info.mdgets theLiteLLM_DailyGatewayRequestsrow in the table listingMerge order
Merge after BerriAI/litellm#35717, which ships the endpoint and the table this describes