retrieving-mlflow-traces

From README

Retrieving MLflow Traces Bound Unity Catalog Searches by Time When searching traces stored in Unity Catalog, include trace.timestampms >= in the filter string, with an upper bound when known. This also applies when searching by experiment ID, run ID, session, or other filters: a small result limit does not prevent a scan across the full trace history. In Python, pass the time condition through filterstring; mlflow.searchtraces() has no starttime argument. Use the time window requested by the user or established by the run or incident. For verification, record the time immediately before the instrumented run. Do not silently restrict historical investigations to the last hour. If the relevant period cannot be determined, ask for it before starting a broad UC search. The examples below demonstrate individual filters; combine them with the relevant time bounds for UC.