Skip to content

docs: fix symbol sets link in error tracking upload guides#16371

Merged
christiaan-ph merged 5 commits into
masterfrom
docs/fix-error-tracking-symbol-sets-link
Apr 16, 2026
Merged

docs: fix symbol sets link in error tracking upload guides#16371
christiaan-ph merged 5 commits into
masterfrom
docs/fix-error-tracking-symbol-sets-link

Conversation

@christiaan-ph
Copy link
Copy Markdown
Contributor

@christiaan-ph christiaan-ph commented Apr 15, 2026

Error tracking configuration was moved to a dedicated /error_tracking/configuration route with a banner on the old settings page pointing users there PostHog/posthog#54507 (merged 2026-04-14). Sweep every error tracking doc that was still linking to the old locations, drop the hardcoded project/2 segment from PostHog app links so they resolve to the current user's project via addProjectIdIfMissing, and clean up a handful of smaller pre-existing issues spotted along the way.

Changes

Symbol sets link (the original reported issue):

  • Update the shared StepVerifySymbolSetsUpload snippet to point at https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets. Since it's a shared snippet, this fixes the broken "Check symbol sets in PostHog" button on all the upload guides that use it:
    • upload-source-maps/{ios,web,node,react,react-native,cli}
    • upload-mappings/android

Upload guides that inlined the same broken URL instead of using the shared snippet:

  • upload-source-maps/github-actions.mdx
  • upload-source-maps/rollup.mdx
  • upload-source-maps/nextjs.mdx
  • upload-source-maps/vite.mdx
  • upload-source-maps/angular.mdx
  • upload-source-maps/webpack.mdx
  • upload-source-maps/nuxt.mdx (also drops a dead StepVerifySymbolSetsUpload import that was never rendered)

Other error tracking docs pointing at the old /error_tracking?activeTab=configuration URL or leaking project/2:

  • troubleshooting.mdx (exception autocapture + symbol sets links)
  • spikes.mdx (spike detection configuration link)
  • grouping-issues.mdx (custom grouping rules)
  • assigning-issues.mdx (auto assignment rules)
  • alerts.mdx (alerting) and the unrelated in-app support panel link on the same page
  • pricing.mdx (disable exception autocapture)
  • capture.mdx (enable exception autocapture)
  • stack-traces.mdx (symbol sets link + in-app support panel link)
  • _snippets/suppression-rules.mdx (shared snippet used from several SDK installation guides)
  • _snippets/web-install-error-tracking.mdx (also fixes a pre-existing broken hash, the correct setting id is error-tracking-exception-autocapture, not exception-autocapture)

Tutorial:

  • tutorials/react-error-tracking.md

Intentionally not changed:

  • integrations.mdx still links to /settings/project-error-tracking. Integrations is the one error tracking setting that stayed on the old environment settings page and did not move to the new configuration route, so these links are still functionally correct.

All PostHog app links in the error tracking docs now use the domain-neutral https://app.posthog.com/... form with no hardcoded project id, relying on the frontend's addProjectIdIfMissing helper to inject the current user's project. No visual or copy changes beyond the URLs themselves.

Checklist

  • I've read the docs and/or content style guides.
  • Words are spelled using American English
  • Use relative URLs for internal links
  • I've checked the pages added or changed in the Vercel preview build
  • If I moved a page, I added a redirect in vercel.json (NOT APPLICABLE)

Point "Check symbol sets in PostHog" to the current error tracking
configuration tab URL, matching the convention used elsewhere in the
error tracking docs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 15, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Apr 15, 2026 05:32PM

@christiaan-ph christiaan-ph requested review from a team and marandaneto and removed request for marandaneto April 15, 2026 11:34
Comment thread contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx Outdated
Error tracking configuration moved from the Settings page and the
in-product Configuration tab to a dedicated /error_tracking/configuration
route (PostHog/posthog#54507). Update all error tracking docs to point
at the new canonical URL and remove the hardcoded project/2 segment,
relying on the app's addProjectIdIfMissing redirect so the URL resolves
to the user's own project.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 15, 2026

Vale prose linter → found 5 errors, 37 warnings, 2 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/error-tracking/_snippets/web-install-error-tracking.mdx — 0 errors, 3 warnings, 0 suggestions
Line Severity Message Rule
1:166 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
1:172 warning 'tracking's' is a possible misspelling. PostHogBase.Spelling
3:73 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/alerts.mdx — 1 errors, 5 warnings, 1 suggestions
Line Severity Message Rule
2:13 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
9:55 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
9:61 warning 'tracking's' is a possible misspelling. PostHogBase.Spelling
37:75 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
43:7 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
49:47 warning Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept. PostHogBase.ProductNames
75:37 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
contents/docs/error-tracking/assigning-issues.mdx — 0 errors, 4 warnings, 0 suggestions
Line Severity Message Rule
5:1 warning Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. PostHogBase.ProductNames
18:12 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
33:98 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
62:43 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/capture.mdx — 1 errors, 3 warnings, 1 suggestions
Line Severity Message Rule
19:49 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
31:46 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
61:141 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
130:428 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
369:101 warning 'runtime's' is a possible misspelling. PostHogBase.Spelling
contents/docs/error-tracking/grouping-issues.mdx — 0 errors, 2 warnings, 0 suggestions
Line Severity Message Rule
32:46 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
49:43 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/pricing.mdx — 0 errors, 3 warnings, 0 suggestions
Line Severity Message Rule
18:88 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
22:1 warning Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. PostHogBase.ProductNames
31:107 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/spikes.mdx — 2 errors, 1 warnings, 0 suggestions
Line Severity Message Rule
7:159 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
28:43 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
43:109 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
contents/docs/error-tracking/stack-traces.mdx — 0 errors, 7 warnings, 0 suggestions
Line Severity Message Rule
7:1 warning Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. PostHogBase.ProductNames
7:113 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
34:1 warning Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. PostHogBase.ProductNames
34:208 warning 'sourcemaps' is a possible misspelling. PostHogBase.Spelling
43:64 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
60:92 warning 'symbolification' is a possible misspelling. PostHogBase.Spelling
64:86 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/troubleshooting.mdx — 0 errors, 2 warnings, 0 suggestions
Line Severity Message Rule
7:4 warning 'Have a question? Ask PostHog AI' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
63:4 warning ''Non-Error promise rejection' with no stack trace' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
contents/docs/error-tracking/upload-source-maps/github-actions.mdx — 0 errors, 1 warnings, 0 suggestions
Line Severity Message Rule
65:43 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/docs/error-tracking/upload-source-maps/nuxt.mdx — 1 errors, 1 warnings, 0 suggestions
Line Severity Message Rule
13:33 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
13:54 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
contents/tutorials/react-error-tracking.md — 0 errors, 5 warnings, 0 suggestions
Line Severity Message Rule
2:28 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
10:54 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
67:4 warning '2. Setting up PostHog for error tracking' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
67:30 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
154:68 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames

@christiaan-ph
Copy link
Copy Markdown
Contributor Author

I'm actually seeing a lot more places across the error tracking docs that have old / broken links, so I'm going to do a sweep to update these too, then will do some final testing

christiaan-ph and others added 2 commits April 15, 2026 14:00
Update the rest of the error tracking docs that inlined the old
/settings/project-error-tracking or /error_tracking?activeTab=configuration
URLs. All of them now point at the canonical /error_tracking/configuration
page with the right selectedSetting hash. Also drop a dead snippet import
from nuxt.mdx and fix the pre-existing broken #exception-autocapture hash
in web-install-error-tracking.mdx (the correct setting id is
error-tracking-exception-autocapture).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@christiaan-ph
Copy link
Copy Markdown
Contributor Author

Blocked by #16236

@christiaan-ph
Copy link
Copy Markdown
Contributor Author

christiaan-ph commented Apr 16, 2026

Test site is built, time for manual testing...
https://b38e07a7.posthog-preview.pages.dev

Plan: For each item, click the link/button and confirm it opens the expected PostHog app page.

"Check symbol sets in PostHog" button — shared snippet

Expected destination: https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets

Upload guides with inlined (non-snippet) buttons

Same expected destination as above.

Other error tracking doc pages

  • troubleshooting
    • "Configuration page" link in "Exceptions not appearing" → #selectedSetting=error-tracking-exception-autocapture
    • "Error Tracking" link in "Source maps not resolving" → #selectedSetting=error-tracking-symbol-sets
  • spikes
    • "error tracking configuration page" → #selectedSetting=error-tracking-spike-detection
    • "alerts tab" in "Getting notified about spikes" → #selectedSetting=error-tracking-spike-detection
  • grouping-issues — "error tracking settings" → #selectedSetting=error-tracking-custom-grouping
  • assigning-issues — "error tracking settings" → #selectedSetting=error-tracking-auto-assignment
  • alerts
    • "error tracking's configuration page" → #selectedSetting=error-tracking-alerting
    • "let us know in-app" → https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse
  • pricing — "project settings" → #selectedSetting=error-tracking-exception-autocapture
  • capture — "enabled exception auto capture" → #selectedSetting=error-tracking-exception-autocapture
  • stack-traces
    • "error tracking settings" → #selectedSetting=error-tracking-symbol-sets
    • "let us know in-app" → https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse

Shared suppression-rules snippet rendered in context

The "configuring suppression rules" link should point to #selectedSetting=error-tracking-suppression-rules on both pages.

Tutorial

@christiaan-ph christiaan-ph requested review from a team, ablaszkiewicz, cat-ph and hpouillot April 16, 2026 09:48
@hpouillot hpouillot requested a review from ReeceJones April 16, 2026 09:54
Copy link
Copy Markdown
Contributor

@hpouillot hpouillot left a comment

Choose a reason for hiding this comment

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

Looks good, thanks a lot !

@christiaan-ph christiaan-ph merged commit e2efe67 into master Apr 16, 2026
20 checks passed
@christiaan-ph christiaan-ph deleted the docs/fix-error-tracking-symbol-sets-link branch April 16, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants