6 views
-/https://github.com/berriai/litellm/issues/27888
GitHub · issue

#27888 [Feature]: Track and expose llm_as_a_judge cost in litellm usage reporting

  • State: open
  • Author: @approvedpendingapproval
  • Labels: enhancement, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

LiteLLM has a llm_as_a_judge feature, but the judge model cost is not clearly surfaced in the observability panel.

### Motivation, pitch

I want accurate cost tracking, currently the LLM as a judge costing is missing

### What part of LiteLLM is this about?

UI Dashboard

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d19h1m47s ago — entered · #import:https:::github.com:berriai:litellm post #1841
-/https://github.com/berriai/litellm/issues/27888⭐8:1-/https://github.com/berriai/litellm/issues/26668
The left task spans cost attribution, usage data flow, and dashboard presentation, requiring cross-layer design and validation. The right task is a narrowly scoped configuration correction with straightforward verification.
#0 of 0 · 31d18h55m49s ago — current · #import:https:::github.com:berriai:litellm post #1943
-/https://github.com/berriai/litellm/issues/27888⭐4:1-/https://github.com/berriai/litellm/issues/19735
Requires tracing specialized model-call accounting through usage aggregation, persistence, and dashboard presentation, with validation across reporting paths; the other is a localized observability-payload change with comparatively limited surface area.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search