Add span status filter support to traces UI#20541
Merged
serena-ruan merged 3 commits intomasterfrom Feb 6, 2026
Merged
Conversation
This was referenced Feb 3, 2026
Contributor
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
Collaborator
Author
|
/polish |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds UI support for filtering traces by span status (OK, ERROR, UNSET), building on backend support added in PR #20540. The PR also refactors URL generation utilities for assessment chart tooltips to improve maintainability.
Changes:
- Added span status filter support to the traces table UI with EQUALS and NOT_EQUALS operators
- Refactored URL generation functions for assessment charts to support flexible filter composition
- Enhanced assessment chart tooltips to link to traces filtered by time range and assessment existence
- Fixed backend span filter logic to ensure multiple conditions apply to the same span
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
tests/store/tracking/test_sqlalchemy_store.py |
Added test verifying span filters correctly match conditions on the same span |
mlflow/store/tracking/sqlalchemy_store.py |
Fixed span filter combination to apply all conditions to the same span via single subquery |
mlflow/server/js/src/shared/web-shared/genai-traces-table/hooks/useTableColumns.tsx |
Added SPAN_STATUS_COLUMN_ID constant for span status filtering |
mlflow/server/js/src/shared/web-shared/genai-traces-table/hooks/useMlflowTraces.tsx |
Added span status filter handling in filter string generation |
mlflow/server/js/src/shared/web-shared/genai-traces-table/hooks/useMlflowTraces.test.tsx |
Added test for span status filter with EQUALS operator |
mlflow/server/js/src/shared/web-shared/genai-traces-table/components/filters/TableFilterItem.tsx |
Added span status to available filter options with EQUALS/NOT_EQUALS operators |
mlflow/server/js/src/experiment-tracking/pages/experiment-overview/hooks/useTraceAssessmentChartData.ts |
Added timestampMs field to chart data points for time-based navigation |
mlflow/server/js/src/experiment-tracking/pages/experiment-overview/components/TraceAssessmentChart.tsx |
Enhanced time series tooltip to link to traces filtered by time and assessment |
mlflow/server/js/src/experiment-tracking/pages/experiment-overview/components/OverviewChartComponents.tsx |
Refactored URL generation with helper functions for flexible filter composition |
mlflow/server/js/src/experiment-tracking/pages/experiment-overview/components/OverviewChartComponents.test.tsx |
Updated tests to reflect refactored URL generation functions |
Contributor
|
Documentation preview for 1a659fc is available at: More info
|
afb7725 to
16d81a4
Compare
hubertzub-db
approved these changes
Feb 4, 2026
31 tasks
Signed-off-by: Serena Ruan <serena.rxy@gmail.com>
Signed-off-by: Serena Ruan <serena.rxy@gmail.com>
16d81a4 to
1a659fc
Compare
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.
🥞 Stacked PR
Use this link to review incremental changes.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Support span status filter since backend already supports it
Screen.Recording.2026-02-03.at.8.51.34.PM.mov
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.