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

#23636 Proxy UI shows 'Request/Response Data Not Available' even with store_prompts_in_spend_logs=true (data stored in proxy_server_request, not messages)

  • State: open
  • Author: @ThePlenkov

### What happened? After upgrading LiteLLM proxy, the Spend Logs UI frequently shows:

> Request/Response Data Not Available

with instructions to enable:

```yaml general_settings: store_model_in_db: true store_prompts_in_spend_logs: true ```

But these settings are already enabled, and prompt data is still being stored (just not in the expected field).

### Environment - LiteLLM image: `docker.litellm.ai/berriai/litellm:main-latest` - LiteLLM package version in container: `1.82.1` - Postgres: `15.17-alpine` - Redis: `7.4-alpine`

### Relevant config ```yaml general_settings: master_key: os.environ/LITELLM_MASTER_KEY api_key: os.environ/LITELLM_API_KEY database_url: os.environ/DATABASE_URL store_model_in_db: true store_prompts_in_spend_logs: true ```

### Reproduction 1. Start proxy with the above config. 2. Send a normal request via `/v1/chat/completions`. 3. Open Spend Logs UI and click request details. 4. Banner appears for many rows saying request/response data is unavailable.

### What I observed in DB For a fresh request (`request_id = 0852eecf-87a5-40a9-a567-dd552a69ce90`): - `messages` is `{}` - `proxy_server_request` is populated (contains input messages) - …

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h22m33s ago — entered · #import:https:::github.com:berriai:litellm post #2479
23636 is harder because it likely requires coordinating persistence-field semantics, proxy data flow, API responses, and Spend Logs UI behavior, with compatibility and regression risks. 32184 is a narrow catalog-data correction with limited validation and scope.
#0 of 0 · 31d17h47m30s ago — current · #import:https:::github.com:berriai:litellm post #3084
Nested group composition has broader architectural scope, affecting configuration resolution, routing semantics, validation, and compatibility testing; the other is comparatively localized to data retrieval and UI presentation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search