MLflow tracing
The shipped configuration enables tracing against a local MLflow server athttp://127.0.0.1:5001.
config/fleet.toml
fleet cli starts an MLflow server for you. It stores data in .fleet_rlm/mlflow/mlflow.db and fails if a server already on that port runs a different MLflow version than the pinned one.
To trace to Databricks, set tracking_uri = "databricks", authenticate with DATABRICKS_HOST and DATABRICKS_TOKEN, and set the optional trace destination keys: trace_catalog, trace_schema, trace_table_prefix, and tracing_sql_warehouse_id.
Find a trace
Withexpose_trace_id = true, turn_start and turn_finish carry a traceId. In the terminal, run /trace to print the trace ID and Run ID.
Control trace content
Record feedback
Attach a thumbs-up or thumbs-down to a trace from the terminal:comment is optional and limited to 2,000 characters.
Runtime Event captures
Fleet writes one capture file per Run at<data_root>/captures/<session_id>/<run_id>.jsonl, so a Turn’s streamed events survive a client disconnect.
config/fleet.toml
retention_days, then keeps only the newest max_captures.
PostHog analytics
Setposthog.enabled = true and put the project token in the variable named by posthog.project_token_env. The shipped configuration uses POSTHOG_PROJECT_TOKEN and the EU host https://eu.i.posthog.com.