Skip to content

[Doc] Tracing quick start#19086

Merged
kevin-lyn merged 8 commits intomlflow:masterfrom
kevin-lyn:doc-tracing-quickstart
Dec 3, 2025
Merged

[Doc] Tracing quick start#19086
kevin-lyn merged 8 commits intomlflow:masterfrom
kevin-lyn:doc-tracing-quickstart

Conversation

@kevin-lyn
Copy link
Member

@kevin-lyn kevin-lyn commented Nov 27, 2025

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19086/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19086/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19086/merge

  • Update the "setup" guide to focus on MLflow server setup.
  • Simplify the tracing quick start guide to focus on sending one trace.
  • Combine python & typescript tracing quickstart.
  • Although it's not a hard requirement, guide the user to create one experiment for each GenAI application.

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How 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" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should 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?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@kevin-lyn kevin-lyn added the team-review Trigger a team review request label Nov 27, 2025
@kevin-lyn kevin-lyn marked this pull request as ready for review November 27, 2025 13:10
@github-actions github-actions bot added area/docs Documentation issues rn/none List under Small Changes in Changelogs. labels Nov 27, 2025
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@github-actions
Copy link
Contributor

github-actions bot commented Nov 27, 2025

Documentation preview for d310578 is available at:

Changed Pages (13)
More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@serena-ruan
Copy link
Collaborator

Interestingly self-hosting is a standalone page, could we fix this so it's part of the original sidebar?
image

Comment on lines +72 to +76
# Specify the tracking URI for the MLflow server.
mlflow.set_tracking_uri("http://localhost:5000")

# Specify the experiment you just created for your GenAI application.
mlflow.set_experiment("My Application")
Copy link
Collaborator

@serena-ruan serena-ruan Nov 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder whether setting env vars with MLFLOW_TRACKING_URI and MLFLOW_EXPERIMENT_ID is better 🤔 In that way we can avoid teaching new users to use 'set_experiment' from the beginning

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which one do we recommend?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no difference imo. But to your point that we only want to include tracing code here, then probably setting env var is better.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think as a required step to finish this tracing quick start, introducing env var here does not bring value though - unless there is specific thing we want to educate the users about.

@kevin-lyn
Copy link
Member Author

@serena-ruan I think the reason self-hosting is a separate top nav is because it's shared between classic and GenAI, but I agree we should fix it and move to the sidebar. let's fix it separately.

@B-Step62
Copy link
Collaborator

B-Step62 commented Dec 1, 2025

@kevin-lyn @serena-ruan I think we should have self-hosted doc as a stand-slone nav to avoid coomplicating the contents. This is common pattern we can see from the other tools' documentation.

@serena-ruan
Copy link
Collaborator

@kevin-lyn @serena-ruan I think we should have self-hosted doc as a stand-slone nav to avoid coomplicating the contents. This is common pattern we can see from the other tools' documentation.

Oh now I noticed it's on the top header, yea that's fine. Previously I thought there's no direct main entry point :)

Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@kevin-lyn kevin-lyn changed the title [Draft] Tracing quick start [Doc] Tracing quick start Dec 2, 2025
@kevin-lyn kevin-lyn requested review from B-Step62 and harupy December 2, 2025 00:24
@kevin-lyn kevin-lyn requested a review from serena-ruan December 2, 2025 00:24
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
Copy link
Collaborator

@serena-ruan serena-ruan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@kevin-lyn kevin-lyn enabled auto-merge December 2, 2025 15:14
@kevin-lyn
Copy link
Member Author

Changes after PR approved: remove the old quick start for python & typescript and added redirection. Some content about typescript is missing due to the removal and will be fixed in followup PRs.

Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@kevin-lyn kevin-lyn added this pull request to the merge queue Dec 3, 2025
Merged via the queue into mlflow:master with commit c52f68c Dec 3, 2025
46 checks passed
@kevin-lyn kevin-lyn deleted the doc-tracing-quickstart branch December 3, 2025 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Documentation issues rn/none List under Small Changes in Changelogs. team-review Trigger a team review request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants