[LEADS-557] Document MLflow storage backend setup and behavior - #296
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (4)
WalkthroughMLflow is documented as an optional storage backend, with configuration examples, logging behavior, error handling, and UI guidance. README and evaluation documentation now reference Langfuse and MLflow storage and export options. ChangesMLflow storage documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/configuration.md`:
- Around line 476-483: Update the MLflow configuration documentation near the
tracing and results logging table to add a prominent warning that queries,
responses, expected values, reasons, and metadata may contain PII or secrets and
are sent to the external MLflow backend. Document retention considerations and
provide guidance to redact sensitive fields or disable tracing/logging before
recommending this setup.
- Around line 468-470: Update the MLflow documentation blockquote near the
“Tracking URI” and “Error handling” paragraphs to keep it contiguous: either
prefix the blank line with the blockquote marker or remove the blank line,
ensuring MD028 passes.
- Around line 489-493: Update the MLflow UI documentation example to remove the
remote MLFLOW_TRACKING_URI value from --backend-store-uri. Clarify that an
existing remote tracking server’s UI should be opened directly, while locally
starting mlflow ui requires a local backend/store URI.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: d940ea6a-83a9-46ca-8f70-02bb4f455b39
📒 Files selected for processing (4)
README.mdconfig/system.yamldocs/EVALUATION_GUIDE.mddocs/configuration.md
xmican10
left a comment
There was a problem hiding this comment.
Thanks!! LGTM, noted potentional typos..
Description
Type of change
Tools used to create PR
Identify any AI code assistants used in this PR (for transparency and review context)
Related Tickets & Documents
Checklist before requesting a review
Testing
Summary by CodeRabbit
score=Noneoutcomes and described MLflow/Langfuse error-handling behavior.