docs: update OpenWebUI integration for Langfuse v4 - #3503
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
The upstream migration is now published as open-webui/pipelines#608 from commit |
dosubot
Bot
added
size:S
|
@claude review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3dc02f708d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ``` | ||
| https://github.com/open-webui/pipelines/blob/main/examples/filters/langfuse_v3_filter_pipeline.py | ||
| https://github.com/open-webui/pipelines/blob/main/examples/filters/langfuse_v4_filter_pipeline.py |
There was a problem hiding this comment.
If this documentation lands before open-webui/pipelines#608 merges, this newly referenced file is absent from upstream main—as the commit's Dependency section itself notes—so the link returns 404 and the installation step cannot be completed. Keep the v3 instructions, point to an existing ref, or block this commit from landing until the upstream file is available.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed in this run: open-webui/pipelines#608 is still open, so the v4 pipeline file is not yet available on upstream main. The PR's stated merge gate remains in effect; no documentation change is appropriate until that external dependency merges.
| [Pipelines](https://github.com/open-webui/pipelines/) is OpenWebUI's UI-agnostic framework for OpenAI API plugins. It can inject plugins that intercept, process, and forward user prompts to the final LLM. | ||
|
|
||
| To trace your application data with Langfuse, you can use the [Langfuse pipeline](https://github.com/open-webui/pipelines/blob/039f9c54f8e9f9bcbabde02c2c853e80d25c79e4/examples/filters/langfuse_v3_filter_pipeline.py), which enables real-time monitoring and analysis of message interactions. | ||
| To trace your application data with Langfuse, install the [Langfuse v4 filter pipeline](https://github.com/open-webui/pipelines/blob/main/examples/filters/langfuse_v4_filter_pipeline.py). It uses the OpenTelemetry-based Langfuse Python SDK v4 and declares `langfuse~=4.7`, the pip-compatible constraint for Langfuse versions `>=4.7,<5`. |
There was a problem hiding this comment.
The commit message includes the internal ID LFE-14968 and its Linear URL, which will expose repository readers to an inaccessible internal reference and directly violates the repository rule forbidding ticket IDs and Linear URLs in commit messages. Rewrite the message to describe the dependency without the internal reference.
AGENTS.md reference: AGENTS.md:L117-L117
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
I do not think a history rewrite is justified here. The PR’s three published commit messages contain no Linear ID or URL, and AGENTS.md line 117 is blank; the Linear reference is in the PR body, not a commit message. Rewriting published history would add churn without addressing the stated concern.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
I reviewed this PR and didn't find any bugs. Because the PR description states this must not merge until the upstream open-webui/pipelines#608 PR lands (the new langfuse_v4_filter_pipeline.py URL doesn't exist on main yet), a human should confirm that dependency is satisfied before merging.
What was reviewed: the updated pipeline install URL and version constraint text, the v3→v4 migration wording (trace/observation/session/user/token semantics), and the streaming-usage callout. Checked whether link-check would catch the not-yet-existing upstream URL — it wouldn't, since that's an external GitHub link outside this repo's build, not a docs bug.
Extended reasoning...
This is a single-file, documentation-only change to content/integrations/no-code/openwebui.mdx updating the OpenWebUI integration guide from the Langfuse v3 to v4 filter pipeline. No application code, security-sensitive logic, or CODEOWNER-restricted paths are touched.
Security risk is essentially none — this only changes prose and a GitHub URL reference in docs. The main non-security consideration is a merge-timing dependency explicitly called out by the author: the new pipeline URL (blob/main/examples/filters/langfuse_v4_filter_pipeline.py) does not exist upstream until open-webui/pipelines#608 merges. The author has already tracked this and posted an update noting the upstream PR is now published, but confirming it's actually merged before this PR merges is outside what an automated content review can verify.
Given the low blast radius (docs prose + one external link) but the presence of an explicit external dependency gating mergeability, I'm deferring rather than approving outright — not because of a code-quality concern, but so a human confirms the upstream dependency is resolved at merge time. No md-override file exists for this route, so that synchronization rule doesn't apply. Formatting and H1 checks were already verified by the author per the PR description.
1 participant
Summary
langfuse~=4.7(pip-equivalent to>=4.7,<5) and OpenTelemetry-based behaviorDependency
This documentation must not merge until open-webui/pipelines#608 is merged, because the new
langfuse_v4_filter_pipeline.pyURL does not exist on upstreammainyet.Linear: LFE-14968
Verification
pnpm run formatpnpm run format:check—All matched files use Prettier code style!node scripts/check-h1-headings.js—Success: All checked markdown/MDX files have at most one H1 heading.The checkout uses Node.js 24 while the repository declares Node.js 22; the focused content checks still passed.
Note
Low Risk
Documentation-only change to an integration guide; no application or security-critical code is modified.
Overview
Updates the OpenWebUI integration guide to use the Langfuse v4 filter pipeline instead of the v3 pipeline.
Documents that the pipeline uses the OpenTelemetry-based Langfuse Python SDK (
langfuse~=4.7), and explains that it groups chat turns into one trace with parented observations, user/session/tags propagation, and optional token usage. Also clarifies post-install key/host setup and lightly cleans up related wording.Reviewed by Cursor Bugbot for commit 3dc02f7. Bugbot is set up for automated code reviews on this repo. Configure here.
Greptile Summary
Updates the OpenWebUI integration guide for the forthcoming Langfuse v4 filter pipeline.
langfuse~=4.7dependency constraint and automatic installation.Confidence Score: 5/5
The documentation appears safe to merge once the explicitly declared upstream pipeline dependency is available.
No unacknowledged actionable defect remains in the changed documentation; the currently unavailable installation target is already identified as a merge-order dependency.
Reviews (1): Last reviewed commit: "docs: clarify OpenWebUI SDK constraint" | Re-trigger Greptile