docs: group debugging, profiling, and OpenTelemetry into a Diagnostics sidebar section#3318
Merged
Conversation
bartlomieju
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Observability and diagnostics topics in the Runtime sidebar were scattered:
Debugging sat under Guides, OpenTelemetry under the Advanced grab-bag, and CPU
profiling was buried as a sub-item of Debugging. They all serve the same user
intent of "my program is running, how do I observe and diagnose it?", so
splitting them across unrelated sections hurt discoverability.
This pulls them into a dedicated "Debugging & observability" section in
runtime/_data.ts containing Debugging, CPU profiling, and OpenTelemetry as
peers. Coverage stays under Testing since it is genuinely test tooling. Only
the sidebar grouping changes; page URLs are untouched.
Closes #3204