Add traces mode to prompts details page and implement filtered traces…#19599
Merged
TomeHirata merged 7 commits intomlflow:masterfrom Jan 5, 2026
Merged
Add traces mode to prompts details page and implement filtered traces…#19599TomeHirata merged 7 commits intomlflow:masterfrom
TomeHirata merged 7 commits intomlflow:masterfrom
Conversation
… view - Introduced a new 'TRACES' mode in the PromptVersionsTableMode enum. - Updated the PromptsDetailsPage to include a button for switching to traces mode. - Added PromptFilteredTracesView component to display traces filtered by the selected prompt version. - Enhanced the usePromptDetailsPageViewState hook to manage traces mode state. - Modified TracesV3Logs to accept initial filters for better trace management. This update improves the user experience by allowing users to view traces associated with specific prompt versions. Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a "Traces" tab to the prompts details page, allowing users to view traces associated with specific prompt versions. When a prompt is experiment-scoped, users can switch to the traces mode to see all traces that were logged with that particular prompt version, with the table automatically filtered by the selected prompt.
Key Changes:
- Added a new TRACES mode to the prompt details page modes (preview, compare, traces)
- Implemented
PromptFilteredTracesViewcomponent that renders the traces table with automatic filtering by prompt version - Extended
TracesV3Logsto acceptinitialFiltersprop for pre-filtering traces
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| utils.ts | Added TRACES enum value to PromptVersionsTableMode |
| usePromptDetailsPageViewState.tsx | Added setTracesMode action and reducer handler for managing traces mode state |
| PromptVersionsTable.tsx | Updated table row selection logic to treat TRACES mode similar to PREVIEW mode (single selection, clickable rows) |
| PromptFilteredTracesView.tsx | New component that displays traces filtered by selected prompt version, with appropriate empty states for non-experiment-scoped prompts |
| PromptsDetailsPage.tsx | Integrated traces mode UI with segmented control button (disabled for non-experiment prompts) and conditional rendering of filtered traces view |
| TracesV3Logs.tsx | Added initialFilters prop and useEffect to apply filters on mount/update for supporting pre-filtered traces views |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
.../js/src/experiment-tracking/components/experiment-page/components/traces-v3/TracesV3Logs.tsx
Outdated
Show resolved
Hide resolved
Contributor
|
Documentation preview for f6a2e01 is available at: More info
|
.../js/src/experiment-tracking/components/experiment-page/components/traces-v3/TracesV3Logs.tsx
Outdated
Show resolved
Hide resolved
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
B-Step62
approved these changes
Jan 5, 2026
omarfarhoud
pushed a commit
to omarfarhoud/mlflow
that referenced
this pull request
Jan 20, 2026
mlflow#19599) Signed-off-by: Tomu Hirata <tomu.hirata@gmail.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.
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
n/a
What changes are proposed in this pull request?
Add a trace tab where users can see traces that are linked to the prompt version.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.