[Doc] Re-arrange tracing sidebar#19329
Conversation
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
There was a problem hiding this comment.
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.mdxandapp-instrumentation/index.mdxpages 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.
|
Documentation preview for a4ef780 is available at: Changed Pages (8)
More info
|
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 = { | |||
| }, | |||
| { | |||
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Oh I'm not proposing adding it into 'Guides', but just within 'tracing' -> 'concepts' -> trace/span
There was a problem hiding this comment.
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.
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
| }, | ||
| { | ||
| type: 'category', | ||
| label: 'OpenTelemetry', |
There was a problem hiding this comment.
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/?
There was a problem hiding this comment.
ya ideally we should have one. I don't have strong opinion on this one. Thoughts @B-Step62 ?
|
Updated tracing sidebar to group guides into sub-categories. cc @B-Step62 |
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
Signed-off-by: Kevin Lin <kevin.lin@databricks.com>
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
#xxxThis PR improves the structure of the "Tracing" sidebar by:
This PR is intentionally NOT to(so that the scope of the PR is not overwhelmed):
What changes are proposed in this pull request?
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould 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?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.