Repository navigation
docs(integrations): RAGFlow tracing (TH-8233) - #1024
Merged
Merged
Conversation
New page /docs/integrations/no-code/ragflow for the per-tenant Future AGI exporter in the future-agi/ragflow fork (PR #1): build from the fork, save keys with /api/v1/futureagi/api-key, the chat/retrieval/LLM span tree, privacy default and redact, failure behaviour, how it differs from RAGFlow's Langfuse and OTEL_HOST settings, tested versions (fork at 2400ca8 / v1.0.0-rc1 tree and merged onto v1.0.0-rc2), limits and troubleshooting. No navigation change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 17, 2026
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
nik13
marked this pull request as ready for review
October 20, 2026 10:43
The card was type-checked, linted and rendered headless with the settings API mocked; the page said it was never rendered or type-checked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Resolve the integration catalog conflict by retaining the RAGFlow status entry alongside all current main entries. Full-stack qualification remains required before publishing a supported guide. Co-Authored-By: Claude Code <noreply@anthropic.com>
nik13
marked this pull request as draft
November 9, 2026 01:33
Replace the outdated rc2 latest-release statement with the verified v1.0.0 availability. The integration remains held pending real deployment qualification. Co-Authored-By: Claude Code <noreply@anthropic.com>
Document the pinned fork image and real settings flow, retain stock-image/version/privacy boundaries, and add customer-wording and built-page regressions. Production image, MySQL/Infinity ingestion and retrieval, browser onboarding, real model chat and Cloud OTLP acceptance have completed. Co-Authored-By: Claude Code <noreply@anthropic.com>
nik13
marked this pull request as ready for review
November 9, 2026 03:55
Co-Authored-By: Claude Code <noreply@anthropic.com>
Link upstream review, replace the obsolete rc1 build with the hardened current-main contribution, and align settings and privacy guidance. Fetch the v1.0.0 tag from upstream because the fork does not publish it. Co-Authored-By: Claude Code <noreply@anthropic.com>
The upstream npm mirror returned repeated HTTP 500 tarball responses in the exact-reader E2B build. Change only registry URLs in the checkout, preserving package versions, integrity hashes and the Dockerfile. Co-Authored-By: Claude Code <noreply@anthropic.com>
Build the unchanged Go and web stages one after another before the production target, matching the resource-safe qualified build sequence. Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
Ready for review
The RAGFlow guide now points to the hardened contribution proposed in infiniflow/ragflow#22183. The exact reader build passes in a fresh E2B sandbox, all eight docs checks are green, and the rendered page has been inspected. Required human review remains outstanding; nothing was merged or published.
00d3e85246abbf2c023233b2dec96eef2222c382.main,5e54cbcc, is an ancestor, merged in1a623d5efd4a16ef2521a31935d7dffd2e62c05e. Both RAGFlow and Langflow catalog entries are preserved.future-agi/ragflow, branchcontrib/futureagi-tracing, exact commit9b2bcb1d1864c75e35ed7d06d3e750725547290e, based on upstreame5a51b680bf11431060e3c4c4f1bc0704b3944c1after v1.0.0.60492deba/ rc1-based image is no longer recommended: it lacks the collector host-policy and provider-error privacy fixes incorporated during upstream review.Customer-facing changes
v1.0.0tag from upstream, because the fork does not publish that tag. Build the unchanged Dockerfile'sgo-builder,web-builderandproductiontargets in sequence to reduce peak memory.GOPROXYargument and the public npm registry. Change only registry origins inweb/.npmrcandweb/package-lock.json; retain locked package versions and integrity hashes.RAGFLOW_IMAGE,DOC_ENGINE=infinity, Infinityv0.7.5-x64-v3, deployment-specific passwords and Admin-port restrictions. Keep the checkout pinned instead of following the upstream README's stock-release checkout step.ALLOW_ANY_HOST=trueon the server container, the Compose recreation command, and the deployment-wide effect on other guarded integrations. It is not a per-tenant setting or collector allowlist.Exact reader-command verification
E2B
rfdocs-reader-1109d: PASS, exit 0; 4 vCPU / 8192 MB; 519 seconds for the reader harness.The harness extracted the page's Bash block verbatim and executed its fetch, checkout, registry-origin substitution and all three Buildx commands, ending with
--target production. No application source or Dockerfile patches were injected, and no provider calls or credentials were staged.9b2bcb1d1864c75e35ed7d06d3e750725547290e.ragflow-futureagi:9b2bcb1d, Linux amd64, 774,878,774 bytes.sha256:19f08c76bd774234f71789d823e9208d124c8fef16260989a1979fc700282e25./ragflow/VERSION:v1.0.0-30-g9b2bcb1d, matching the checkout's release-tag description.web/.npmrcandweb/package-lock.jsonregistry origins differ from the pinned source; package versions, integrity hashes and Dockerfile are unchanged.Final CI and rendering
All eight checks pass on
00d3e85246abbf2c023233b2dec96eef2222c382:Downloaded and inspected the final-head built-page screenshot. The status note is visible above prerequisites; all build commands, the native settings table, collector/privacy guidance and navigation render correctly. No fabricated or unrelated product image was added.
Existing qualification of the pinned RAGFlow source
These completed E2B runs qualify
9b2bcb1d; their application/provider lanes were not rerun by this docs update:rfup3-live-final-1109a: exact production source, two MySQL migrations, browser registration/login and settings save with masked readback, real ingestion/retrieval using Infinity v0.7.5, and one grounded model chat with correctly parentedragflow.chat,ragflow.retrievalandragflow.llmspans. Existing Cloud-forward evidence records collector acceptance; no new Cloud UI verification is claimed.rfup2-fix-live-1109a: same source; default loopback/link-local rejection with zero collector requests, operator opt-in, capture-on synthetic provider-error credential omission, configuration deletion, and pending-export shutdown flush. This security lane made no real provider calls.Earlier reader attempts and their corrections
Failures remain recorded rather than being relabeled as passes:
rfdocs-reader-1109a: failed before checkout because the fork lacksv1.0.0; corrected by fetching the release tag read-only from upstream.rfdocs-reader-1109b: repeated HTTP 500 errors from the upstream npm mirror for locked tarballs, after three attempts. The identical tarball returned HTTP 200 from npmjs.org. Captured diagnostics and stopped the affected build (exit 130); sandbox deletion/404 confirmed. This motivated a registry-origin-only change, not a package upgrade.rfdocs-reader-1109c: the parallel production build reached 8,270,188,544 / 8,343,162,880 bytes of memory, then metrics stopped and command RPCs timed out. Saved metrics, deleted the unresponsive sandbox and verified 404; runner reports exit 94. No kernel OOM log was available. Serializing the unchanged builder targets resolved the reader gate in the successful run above.Evidence and boundaries
/Volumes/nik-ext-1/tmp/traceai-release-20261104/e2b/runs/rfdocs-reader-1109d/receipt.json./Volumes/nik-ext-1/tmp/agent-plugins-1106/rfdocs-reader-final-1109-7xg0kp1t/evidence/./Volumes/nik-ext-1/tmp/agent-plugins-1106/rfdocs-serial-ci-1109-OWjGKv/ragflow-customer-guide.png./Volumes/nik-ext-1/tmp/traceai-release-20261104/e2b/runs/rfdocs-reader-1109a/,rfdocs-reader-1109b/, andrfdocs-reader-1109c/alongside the successful run./Volumes/nik-ext-1/tmp/agent-plugins-1106/ragflow-upstream-1109/rfup3-live-final-1109a-evidence-903oes0m/evidence/and/Volumes/nik-ext-1/tmp/agent-plugins-1106/ragflow-upstream-1109/rfup2-fix-live-1109a-evidence-xj1ua86n/evidence/.This docs PR remains non-draft, ready for review, not merged or published. Upstream #22183 is still under review. No third-party comments, branch writes or merges were made by this docs update. No force-push or branch rename was used. All builds and tests ran in E2B or GitHub Actions, never locally. Existing-database upgrades and capacity testing are not claimed.
🤖 Generated with Claude Code