Skip to content

[Doc] Re-arrange tracing sidebar#19329

Merged
kevin-lyn merged 7 commits intomlflow:masterfrom
kevin-lyn:doc-tracing-sidebar
Dec 16, 2025
Merged

[Doc] Re-arrange tracing sidebar#19329
kevin-lyn merged 7 commits intomlflow:masterfrom
kevin-lyn:doc-tracing-sidebar

Conversation

@kevin-lyn
Copy link
Member

@kevin-lyn kevin-lyn commented Dec 11, 2025

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19329/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19329/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/19329/merge

Related Issues/PRs

#xxx

This PR improves the structure of the "Tracing" sidebar by:

  • Moving all guides into one single "Guides" section.
  • Rename guides title to start with verb so that the user intention clear.
  • Order the guides by trace ingestion -> trace metadata usage -> trace viewing -> others.
  • Remove redundant pages in tracing sidebar.

This PR is intentionally NOT to(so that the scope of the PR is not overwhelmed):

  • Improve the content inside the guides.
  • Remove all duplicate content.
  • Mapping guides to a clear JTBD since it's not yet aligned and we are not sure if it makes sense for tracing.

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>
Copilot AI review requested due to automatic review settings December 11, 2025 08:21
@github-actions github-actions bot added area/docs Documentation issues rn/none List under Small Changes in Changelogs. labels Dec 11, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR reorganizes the MLflow Tracing documentation sidebar to improve navigation and clarity. The main objective is to consolidate scattered guides into a single "Guides" section, rename guides with action-oriented verbs, and remove redundant documentation pages.

Key Changes:

  • Consolidated all tracing guides under a single "Guides" section with verb-based titles (e.g., "Enable Automatic Tracing", "Tag Traces")
  • Removed the standalone typescript-sdk.mdx and app-instrumentation/index.mdx pages with proper redirects configured to the quickstart page
  • Updated all TypeScript library documentation links to point to the unified quickstart guide

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated no comments.

Show a summary per file
File Description
docs/sidebarsGenAI.ts Restructured the tracing sidebar by consolidating guides, adding verb-based labels, removing nested category structure, and deleting redundant sections
docs/docusaurus.config.ts Added redirects for removed pages (typescript-sdk, app-instrumentation) to the quickstart page, consolidated duplicate redirect rules
libs/typescript/*/README.md Updated documentation links from the old typescript-sdk page to the quickstart page across all TypeScript packages
libs/typescript/integrations/openai/docs/index.html Updated HTML documentation link to point to the quickstart page
docs/docs/genai/tracing/integrations/contribute.mdx Updated internal documentation reference from the old app-instrumentation page to the automatic tracing guide
docs/docs/genai/tracing/app-instrumentation/opentelemetry.mdx Removed redundant sidebar label property
docs/docs/genai/tracing/app-instrumentation/typescript-sdk.mdx Deleted page with redirect configured to quickstart
docs/docs/genai/tracing/app-instrumentation/index.mdx Deleted page with redirect configured to quickstart

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 11, 2025

Documentation preview for a4ef780 is available at:

Changed Pages (8)
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.

kevin-lyn and others added 2 commits December 11, 2025 17:40
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
@@ -47,29 +47,69 @@ const sidebarsGenAI: SidebarsConfig = {
},
{
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we also add concepts section and move them into this folder? Currently it's in https://pr-19329--mlflow-docs-preview.netlify.app/docs/latest/genai/concepts/trace/ and I feel like users may never check that

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 for "reference" like documentation, "Concepts" in this case, it should not be a required page for user. Users should be able to under stand what "trace" is by reading through quick start and other guides.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Users should be able to under stand what "trace" is by reading through quick start and other guides.

Why do you think so? I think having a page explaining what it is is more straightforward than asking users to get a sense of what it is after reading through a bunch of guides. Basically in landing page (https://pr-19329--mlflow-docs-preview.netlify.app/docs/latest/genai/tracing/) it never explains what traces/spans are

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 having a page explaining what it is is more straightforward

I agree on this one but for new users, I don't think reading a "concept" explanation is what they are looking for. What new users are looking for is to understand the value props of MLflow as quick as possible.
I see your point in terms of discoverability of the "Concepts" since it's currently at the bottom. But moving "Concepts" into "Guides" also defeats the purpose of guides though.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh I'm not proposing adding it into 'Guides', but just within 'tracing' -> 'concepts' -> trace/span

Copy link
Member Author

Choose a reason for hiding this comment

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

Got it. we can revisit this separately, if we can align on having "Concepts" as a sub-category, then we should have it for all other core components, so that it's consistent.

kevin-lyn and others added 2 commits December 12, 2025 13:11
},
{
type: 'category',
label: 'OpenTelemetry',
Copy link
Collaborator

Choose a reason for hiding this comment

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

Happy to discuss but personally I feel it's unexpected that OpenTelemetry is at the same level as guides/integrations etc. We can probably combine it with https://pr-19329--mlflow-docs-preview.netlify.app/docs/latest/genai/tracing/app-instrumentation/opentelemetry/?

Copy link
Member Author

Choose a reason for hiding this comment

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

ya ideally we should have one. I don't have strong opinion on this one. Thoughts @B-Step62 ?

@kevin-lyn
Copy link
Member Author

Updated tracing sidebar to group guides into sub-categories. cc @B-Step62

Copy link
Collaborator

@B-Step62 B-Step62 left a comment

Choose a reason for hiding this comment

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

LGTM!

@kevin-lyn kevin-lyn enabled auto-merge December 16, 2025 05:50
@kevin-lyn kevin-lyn added this pull request to the merge queue Dec 16, 2025
Merged via the queue into mlflow:master with commit db4fc95 Dec 16, 2025
53 of 54 checks passed
@kevin-lyn kevin-lyn deleted the doc-tracing-sidebar branch December 16, 2025 06:11
WeichenXu123 pushed a commit to WeichenXu123/mlflow that referenced this pull request Dec 19, 2025
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
WeichenXu123 pushed a commit that referenced this pull request Dec 19, 2025
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
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. v3.8.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants