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

#25628 [Bug]: langfuse_otel callback logs raw upstream model name instead of proxy alias for streaming requests

  • State: open
  • Author: @zarzouram
  • 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 using the `langfuse_otel` callback with LiteLLM proxy and a model configured with a proxy alias (e.g. `groq-gpt-oss-120b` → `groq/openai/gpt-oss-120b`), **streaming requests** log the raw upstream model identifier (`openai/gpt-oss-120b`) in Langfuse instead of the configured proxy alias (`groq-gpt-oss-120b`).

Non-streaming requests work correctly and log the proxy alias.

Expected: Langfuse traces show the proxy alias (`groq-gpt-oss-120b`) for both streaming and non-streaming requests.

### Steps to Reproduce

1. Configure a model alias in config.yaml:

```yaml model_list: - model_name: groq-gpt-oss-120b litellm_params: model: groq/openai/gpt-oss-120b api_key: os.environ/GROQ_API_KEY

litellm_settings: callbacks: - langfuse_otel ```

2. Make a streaming request to the proxy:

``` import openai client = openai.OpenAI(base_url="http://localhost:4000", api_key="<master-key>") response = client.chat.completions.create( model="groq-gpt-oss-120b", messages=[{"role": "user", …

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d18h11m12s ago — entered · #import:https:::github.com:berriai:litellm post #2666
Issue #30460 is harder because it involves distributed Redis state, timeout and retry behavior, cross-pod consistency, reconciliation, and budget-enforcement correctness. Issue #25628 is comparatively localized to preserving model-alias metadata through the streaming callback path.
The left task is a repository-wide cross-language migration involving architecture, feature parity, performance validation, deployment, and substantial regression risk. The right task is a narrowly scoped streaming callback mapping bug with localized code changes and targeted tests.
The left issue spans pass-through response handling, guardrail enforcement semantics, raw-to-normalized response translation, and likely multiple response formats, creating broader regression and testing risk. The right issue is comparatively localized to preserving the configured alias through the streaming callback path.
#0 of 0 · 31d17h32m13s ago — current · #import:https:::github.com:berriai:litellm post #3342
A new provider requires broader integration across model discovery, endpoint translation, pricing, usage accounting, configuration, and compatibility testing. The other task is comparatively localized to preserving an existing alias through one streaming observability path, with a narrower regression surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search