7 views
-/https://github.com/berriai/litellm/issues/33210
GitHub · issue

#33210 [Bug]: vLLM passthrough (`/vllm/*`) with router models: request never appears in SpendLogs — "standard_logging_object not found" on every call

  • State: open
  • Author: @antoniovmonge
  • Labels: bug, proxy, llm translation

### Check for existing issues

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

### What happened?

When calling a vLLM passthrough route (e.g. `POST /vllm/pooling`) where the `model` in the request body resolves to a deployment in `model_list`, the request succeeds (200 OK) but is **never recorded in `LiteLLM_SpendLogs`** (and therefore never shows in the UI Logs tab). Every call logs two non-blocking errors: `_PROXY_track_cost_callback` fails with `standard_logging_object not found`, and the Prometheus callback fails with `standard_logging_object is required, got=None`.

The docs state that Logging is supported for vLLM passthrough routes (https://docs.litellm.ai/docs/pass_through/vllm), but with router models nothing is logged at all.

Note this is related to, but distinct from, #24204 / PR #24205: there, `allm_passthrough_route` rows ARE written with `spend: 0.0`. Here the `StandardLoggingPayload` is never built, so the SpendLogs write is aborted entirely and the request is invisible to spend tracking, budgets, and the UI.

### What I found

`vllm_proxy_route` detects the body model as a router model (`is_passthrough_request_using_router…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d17h49m39s ago — entered · #import:https:::github.com:berriai:litellm post #3042
#33210 requires tracing and repairing cross-cutting request-finalization, cost tracking, callback, and persistence behavior across passthrough and router flows, with regression coverage for logging integrations. #32142 is comparatively localized to path interpretation in the MCP server and should require narrower code changes and tests.
#0 of 0 · 31d17h33m58s ago — current · #import:https:::github.com:berriai:litellm post #3311
The left item has broader implementation scope: it requires new cross-provider media normalization, format and metadata handling, validation, and extensive compatibility testing. The right item is primarily a localized logging-pipeline integration fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search