Add user selector in the gateway usage page#20944
Merged
TomeHirata merged 3 commits intomlflow:masterfrom Feb 19, 2026
Merged
Conversation
31 tasks
Contributor
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
17bd52c to
f4294de
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an admin-only “User” selector to the AI Gateway Usage page and plumbs trace-metrics filter expressions through the overview chart stack so charts can be scoped to a selected authenticated user.
Changes:
- Add
/mlflow/users/list(REST + ajax) auth endpoint and an integration test covering admin vs non-admin behavior. - Introduce a
useUsersQueryhook + a user dropdown inGatewayUsagePage, emitting a trace-metadata filter onmlflow.auth.userId. - Extend overview chart context and trace chart data hooks to accept and forward
filtersto trace-metrics queries.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| tests/server/auth/test_auth.py | Adds integration coverage for the new list-users auth endpoint. |
| mlflow/server/auth/routes.py | Declares REST + AJAX route constants for listing users. |
| mlflow/server/auth/init.py | Registers the list-users routes, validator mapping, and handler implementation. |
| mlflow/server/js/src/gateway/hooks/useUsersQuery.ts | Adds a React Query hook for fetching users from the auth ajax endpoint. |
| mlflow/server/js/src/gateway/pages/GatewayUsagePage.tsx | Adds user selection UI and constructs trace-metadata filters passed into charts. |
| mlflow/server/js/src/gateway/components/GatewayChartsPanel.tsx | Wires optional filters prop through to the overview charts provider/query layer. |
| mlflow/server/js/src/experiment-tracking/pages/experiment-overview/OverviewChartContext.tsx | Adds filters to shared chart context. |
| mlflow/server/js/src/experiment-tracking/pages/experiment-overview/hooks/useTrace*.ts | Plumbs filters into trace-metrics queries for requests/latency/errors/tokens/cost. |
| mlflow/server/js/src/shared/web-shared/model-trace-explorer/TraceMetrics.types.ts | Adds helper for building metadata filter expressions + constant for auth user-id metadata key. |
mlflow/server/js/src/shared/web-shared/model-trace-explorer/TraceMetrics.types.ts
Outdated
Show resolved
Hide resolved
Contributor
|
Documentation preview for b81302a is available at: More info
|
5010ace to
46f718b
Compare
TomeHirata
commented
Feb 18, 2026
| </SimpleSelect> | ||
| {isLoadingEndpoints && <Spinner size="small" />} | ||
| </div> | ||
| {!usersError && ( |
Collaborator
Author
There was a problem hiding this comment.
Main change is here
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
9857234 to
9ea099b
Compare
daniellok-db
pushed a commit
to daniellok-db/mlflow
that referenced
this pull request
Feb 20, 2026
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
daniellok-db
pushed a commit
that referenced
this pull request
Feb 20, 2026
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.
🥞 Stacked PR
Use this link to review incremental changes.
Related Issues/PRs
n/a
What changes are proposed in this pull request?
This PR introduces a way to filter gateway usage metrics by user.
How is this PR tested?
Does this PR require documentation update?
Does this PR require updating the MLflow Skills repository?
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.