Data and AI struggles

Trouble with MLflow traces

MLOps4 posts from 3 people3d active+33 posts in the last 7 days, 0 the 7 days before (rising)

Posts per day

Posts per day4 posts, Sep 5 to Oct 25

The posts behind it

4, newest first
GitHub issuesOct 20 5 days ago[BUG] `OTEL_EXPORTER_OTLP_ENDPOINT` gets `/v1/traces` appended even with the gRPC protocol, so scheme-less gRPC endpoints fail to export> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...mlflow/mlflow · MetehanAydemir2 repliesOpen ↗GitHub issuesOct 19 6 days ago[FR] Numeric comparison operators (>, >=, <, <=) for the Feedback filter in the Traces V4 table...and review the low-scoring traces in the UI after each run. > #### Why is it currently difficult to achieve this use case? The backend already supports it. `mlflow/utils/search_utils.py` defines `NUMERIC_ASSESSMENT_COMPARATORS = {">", ">=", " = 0.2 AND feedback.`conciseness` `,...mlflow/mlflow · bennischulz3 repliesOpen ↗GitHub issuesOct 19 6 days ago[FR] Evaluation runs table: column reordering and saved/default views (like Traces V4), and ship the resizable-columns work...the table puts them, often far to the right behind a horizontal scroll. - There is no way to save a column configuration. Hiding columns via **Columns** lasts only until the page reloads, so you have to repeat it every visit. With many metrics this makes the table barely usable....mlflow/mlflow · bennischulz4 repliesOpen ↗GitHub issuesSep 5 7 weeks agoAdd a typed client API to submit Issue Detection for traces> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ## Summary MLflow has...mlflow/mlflow · adamgurary9 repliesOpen ↗

Companies and products named

About this problem

Evidence

4 posts from 3 people in 1 place, about 1 a week over 46 days. Mostly on mlflow/mlflow. Tools named alongside: GitHub.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about MLflow with no known issue, sharing the word "traces". First post Sep 5, 2026, latest Oct 20, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

History

AddedOct 25, 2026Trouble with MLflow traces (4 posts)