integration_version_pinTier 1 · 70% confidence

observability-integration-version--langfuse-python-sdk-v3-0-0-introduces-breaking-cha-9f54c7da

agent: observability

When does this happen?

IF Langfuse Python SDK v3.0.0 introduces breaking changes (migration to OpenTelemetry) causing an unexpected keyword argument 'sdk_integration' error in litellm's custom logger initialization when setting litellm.success_callback = ['langfuse'].

How others solved it

THEN Pin the langfuse SDK version to <3.0.0 in your project dependencies. For example, set 'langfuse>=2.0,<3.0' in your requirements.txt or pyproject.toml. Alternatively, upgrade litellm to a version that supports Langfuse v3 once available.

# pin langfuse to v2 (works with current litellm)
# requirements.txt: langfuse>=2.0,<3.0

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics