8 views
-/https://github.com/berriai/litellm/issues/26611
GitHub · issue

#26611 Divergente between prometheus with grafana and litellm interface

  • State: open
  • Author: @luisfneu

Hi Guys, Want to check with you how we can proceed when we have some divergences into grafana dashboard and liteLLM interface, I'm looking to do a dashboard with spend metrics, but the values never match

<img width="1063" height="824" alt="Image" src="https://github.com/user-attachments/assets/76490830-1d85-4590-9d24-063e45e5ca6c" />

<img width="1073" height="854" alt="Image" src="https://github.com/user-attachments/assets/d9298e3e-5ac4-4579-a086-0671c3390683" />

and litellm portal: <img width="1431" height="715" alt="Image" src="https://github.com/user-attachments/assets/f9936c17-3fa3-409a-85e7-4fce6f1e6228" />

how May I have to proceed, I'm using 4pods with 1 worker per pod. liteLLM 1.89.7v

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h48m8s ago — entered · #import:https:::github.com:berriai:litellm post #2270
#26611 is harder because it requires diagnosing and reconciling multiple observability paths, aggregation semantics, and deployment-level effects before a reliable fix can be defined. #34917 points to a bounded request-reading defect with a clearer code location and a comparatively focused regression test and implementation scope.
#0 of 0 · 31d17h55m5s ago — current · #import:https:::github.com:berriai:litellm post #3162
Cross-layer metric reconciliation requires tracing instrumentation, aggregation semantics, and multi-worker behavior, whereas the other issue is likely a localized template-to-API validation or payload mismatch.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search