Repository navigation
docs(observability): rework the Langfuse SDK to OTel v2 migration guide - #3041
Merged
shivamrawat1 merged 1 commit intoNov 15, 2026
Merged
Conversation
Lead with a breaking changes table that pairs each change with the setting that restores the SDK behavior, then give numbered migration, verification and rollback steps. Legacy field mappings move into one table. Corrects the claim that proxy-wide Langfuse keys are required for key and team projects, which stopped being true in v1.109.0, and adds LITELLM_OTEL_LANGFUSE_DESTINATION_SPAN_SCOPE (#51726).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
shivamrawat1
deleted the
litellm_docs_langfuse_otel_v2_migration_rework
branch
November 15, 2026 02:51
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Langfuse SDK to OTel v2 migration guide was hard to act on. Breaking changes, steps and edge cases were mixed into long paragraphs, so a reader could switch callbacks without noticing that ingestion grows and prompts disappear.
This rewrite puts a breaking changes table first. Each row says what changed, what the reader sees after switching, and the setting that restores the SDK behavior. Five numbered steps follow (prepare, switch the proxy callback, move key and team callbacks, verify on staging, roll out), then rollback, one table of legacy field mappings, and a short section for teams that want the full trace, which keeps the redaction warning. Deep edge cases now link to the OpenTelemetry v2 page instead of being repeated here.
Two content fixes came out of checking the page against main. The old page said key and team projects need proxy-wide Langfuse keys, which stopped being true in v1.109.0, so the guide now describes the keys-only setup. It also adds
LITELLM_OTEL_LANGFUSE_DESTINATION_SPAN_SCOPEfrom BerriAI/litellm#51726, badged as v1.111.0 to match the page's other 1.111.0 badges. That PR merged on 2026-11-14 and is not in a release tag yet, so the badge needs a check once v1.111.0 is cut.scripts/check-docs.py --base=origin/mainreports no problems for the page, and it compiles as MDX with remark-gfm. I did not run the full site build locally.