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

#29937 [Bug]: Prometheus endpoint not show the remaining budget

  • State: open
  • Author: @humpalu
  • Labels: bug

### Check for existing issues

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

### What happened?

Im trying to track the budget consume via the Prometheus endpoint but for the remaining budget always 'Inf' value even I set it on Team level or api key level. I also tried named and numeric settings too.

Here is the output

``` # HELP litellm_remaining_team_budget_metric Remaining budget for team # TYPE litellm_remaining_team_budget_metric gauge litellm_remaining_team_budget_metric{team="1dcf5b89-67e3-46bd-98ce-56f969e300e8",team_alias="MY_TEAM"} +Inf # HELP litellm_team_max_budget_metric Maximum budget set for team # TYPE litellm_team_max_budget_metric gauge litellm_team_max_budget_metric{team="1dcf5b89-67e3-46bd-98ce-56f969e300e8",team_alias="MY_TEAM"} 25.0 ```

### Steps to Reproduce

1. Activate prometheus endpoint with the following config ``` litellm_settings: modify_params: true disable_end_user_cost_tracking: false callbacks: ["prometheus"] prometheus: true prometheus_initialize_budget_metrics: true ``` 2. 3.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

_No response_

### What LiteL…

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h2m28s ago — entered · #import:https:::github.com:berriai:litellm post #1831
The right issue is harder because it spans proxy endpoint behavior, upstream pagination semantics, response compatibility, and likely multiple MCP code paths and integration tests. The left issue appears more localized to budget-state calculation or metric initialization, with narrower validation and lower regression risk.
The Prometheus defect is harder because it requires tracing budget state through spend accounting, persistence, and metric exposition, while resolving edge cases around unset or non-finite values and adding regression coverage. The Bedrock change is comparatively contained to provider request transformation and capability-gated field mapping.
The right issue is harder because it requires tracing budget accounting and metrics-export behavior, reproducing configuration-dependent behavior, and adding regression coverage; the left is a localized metadata synchronization change.
#0 of 0 · 31d18h30m31s ago — current · #import:https:::github.com:berriai:litellm post #2368
The left item is a broad proxy feature spanning centralized configuration, multiple tool integrations, validation, persistence, access control, and rollout behavior. The right item is likely a localized observability/accounting defect involving metric calculation or initialization, with narrower testing and regression scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search