docs: De-duplicate Troubleshooting and Custom Instrumentation page titles - #19301
Open
coolguyzone wants to merge 2 commits into
Open
docs: De-duplicate Troubleshooting and Custom Instrumentation page titles#19301coolguyzone wants to merge 2 commits into
coolguyzone wants to merge 2 commits into
Conversation
…tles Give section-specific troubleshooting pages descriptive titles (Tracing Troubleshooting, Crons Troubleshooting, Profiling Troubleshooting, etc.) so their rendered <title> tags no longer collide within a platform. Each platform's top-level "Troubleshooting" page is left unchanged. Rename the trace-propagation "Custom Instrumentation" pages to "Custom Trace Propagation" to distinguish them from the performance-oriented custom-instrumentation pages. Covers 33 pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Following review feedback: instead of "Custom Trace Propagation" (which mismatched the ~16 inbound links reading "custom instrumentation"), use "Custom Instrumentation for Distributed Tracing". The inbound links read "...set up custom instrumentation for distributed tracing", so they now flow naturally into the page title. Also unifies the JavaScript and Python pages (which already used "Custom Trace Propagation") under the same name so the concept has one title across all platforms, and updates the 3 links that used the old anchor text. 13 pages retitled, 3 links fixed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
philprime
reviewed
Sep 9, 2026
philprime
left a comment
philprime
left a comment
Member
There was a problem hiding this comment.
This change leads to duplication/bloat in the side menu. Do we have a solution to fix the title while keeping the menu clean?
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
2 participants
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.
DESCRIBE YOUR PR
De-duplicates page titles that collide in the rendered
<title>tag. Two systematic families where multiple pages on the same platform rendered an identical title (e.g. Java had four pages all showingTroubleshooting | Sentry for Java):tracing/trace-propagation/custom-instrumentationpages are renamed to "Custom Trace Propagation" to distinguish them from the performance-orientedtracing/instrumentation/custom-instrumentationpages.Covers 33 pages. Note: the site already appends
| Sentry for {Platform}to platform page titles, so cross-platform repeats (e.g. "Configuration") are already unique and were intentionally left alone; this PR only targets genuine within-platform collisions.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: