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

#33383 Upgrade Langfuse integration to Python SDK v4 and v4 OTel ingestion

  • State: open
  • Author: @hassiebp

Hi LiteLLM team 👋 — I'm Hassieb from the Langfuse team.

Langfuse Cloud's [Fast Preview](<https://langfuse.com/docs/v4>) uses the new observations-first ingestion path. For real-time data there, Python integrations should use SDK v4.7.0+ or send compatible OpenTelemetry spans with the v4 ingestion header.

I reviewed LiteLLM's two Langfuse callback paths. The concrete migration looks like:

* Raise the proxy/runtime dependency from `langfuse<3` to `langfuse>=4.7,<5` and update the exact `2.59.7` pins used by proxy builds. * In the `langfuse_otel` callback, add `x-langfuse-ingestion-version: 4` alongside `Authorization` in both the static exporter config and dynamic/per-request headers. The generic OTel Langfuse preset should carry the same header. * Keep the existing OTLP endpoint, but ensure user/session/trace attributes are attached to every exported span so they remain queryable in Fast Preview. * Migrate the legacy `langfuse` callback away from `.trace()/.generation()` to v4 observations plus `propagate_attributes()`, or deprecate that legacy path in favor of `langfuse_otel`. * Update the existing `test_langfuse_otel.py` coverage for the new header and both proxy/SDK callback m…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d19h3m8s ago — entered · #import:https:::github.com:berriai:litellm post #1811
The left task requires coordinated dependency, telemetry, compatibility, and test changes across multiple integration paths; the right is a localized chart-template adjustment with limited scope.
#0 of 0 · 31d18h50m58s ago — current · #import:https:::github.com:berriai:litellm post #2019
The left issue requires concurrency-safe state management, atomicity or reservation semantics, race-condition testing, and careful compatibility with asynchronous cache and budget enforcement paths. The right issue is primarily a versioned SDK/OTel integration migration with configuration and test updates, making it substantially narrower in scope and risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search