scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-22 00:31:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 51

refactor(proxy): drop narrating docstrings from the aggregated usage query path

Browse source 
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This commit is contained in:
yassin 2026-09-16 09:04:37 +00:00
parent b5e2e9a392
commit cfd83548b3
1 changed files with 0 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
litellm/proxy/management_endpoints/common_daily_activity.py
View file

@ -761,13 +761,6 @@ def _build_aggregated_sql_query(
) -> tuple[str, list[str]]: # mutable-ok: SQL text plus its ordered $N params
"""Build the GROUPING SETS query for aggregated daily activity.
One statement, two UNION ALL arms over the same WHERE clause. The first arm is
key-free: grand total, per-date totals and the (date, model / model_group /
provider / mcp / endpoint) rollups, so its row count never grows with the number
of keys. The second arm emits the (date, <dimension>, api_key) rollups for the
USAGE_TOP_API_KEYS_LIMIT highest-spend keys only. Both arms share the 7-bit
group_level bitmask (date, api_key, model, model_group, provider, mcp, endpoint).
Returns:
Tuple of (sql_query, params_list) ready for prisma_client.db.query_raw().
"""
@ -1366,13 +1359,6 @@ async def get_daily_activity_aggregated(
) -> SpendAnalyticsPaginatedResponse:
"""Aggregated variant that returns the full result set (no pagination).
Runs one GROUPING SETS statement with two UNION ALL arms: a key-free one for totals
and the model/provider/mcp/endpoint rollups (row count independent of key
cardinality) and a bounded one for the per-key rollups of the top
USAGE_TOP_API_KEYS_LIMIT keys by spend. breakdown.api_keys and every
api_key_breakdown therefore list at most that many keys, while the totals and the
key-free rollups cover every key.
include_entity_breakdown runs a small companion rollup query and folds
`breakdown.entities` onto the response, as entity-scoped views like Team Usage need.