16 views
-/https://github.com/berriai/litellm/issues/11929
GitHub · issue

#11929 [Bug]: Usage Dashboard: Two Issues with Spend Reporting and Failed Request Attribution

  • State: open
  • Author: @HarpreetBaathTR
  • Labels: bug, mlops user request

### What happened?

We've identified two separate bugs in the LiteLLM usage dashboard that cause incorrect data display:

1. **Frontend Pagination Bug**: Total spend significantly underreported when data spans multiple pages 2. **Backend Provider Attribution Bug**: Failed requests show as 0 for all providers despite actual failures occurring

🔍 Bug Details

### Bug 1: Frontend Pagination Aggregation Issue

**Problem**: The usage dashboard only displays totals from the first page of API results instead of aggregating across all pages.

**API Calls Made**: ``` /user/daily/activity?page=1 → Returns metadata with totals /user/daily/activity?page=2 → Returns metadata with totals /user/daily/activity?page=3 → Returns metadata with totals /user/daily/activity?page=4 → Returns metadata with totals ```

**Expected**: Dashboard should sum all metadata totals across pages **Actual**: Dashboard only shows totals from page 1

**Affected Metrics**: - Total spend - Total API requests - Successful/failed requests - Token usage - Cache statistics

### Bug 2: Backend Provider Attribution Issue

**Problem**: "Spend by Provider" section shows `failed_requests: 0` for all providers despite fail…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d17h55m21s ago — entered · #import:https:::github.com:berriai:litellm post #2809
#11929 spans coordinated frontend aggregation and backend attribution changes with cross-layer testing, while #31682 appears to be a narrower, underspecified error requiring less implementation scope.
#0 of 0 · 31d17h45m43s ago — current · #import:https:::github.com:berriai:litellm post #2979
The dashboard issue is harder because it spans frontend aggregation, backend attribution, API behavior, and end-to-end validation, whereas the Azure issue is comparatively contained within provider parameter translation and version-specific tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search