From 85dcdf77c964ee4327dff4dba9505df580e20ec6 Mon Sep 17 00:00:00 2001 From: Christiaan Hendriksen Date: Wed, 15 Apr 2026 12:24:18 +0100 Subject: [PATCH 1/3] docs: fix symbol sets link in error tracking upload guides 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) --- .../error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx b/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx index b1c886f619d2..128172c27850 100644 --- a/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx +++ b/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx @@ -16,7 +16,7 @@ export const StepVerifySymbolSetsUpload: React.FC Check symbol sets in PostHog From 632526a731c33bf4573f133d7eaee08e00df5b54 Mon Sep 17 00:00:00 2001 From: Christiaan Hendriksen Date: Wed, 15 Apr 2026 13:41:52 +0100 Subject: [PATCH 2/3] docs: use new error tracking configuration route, drop project id 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) --- .../error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx | 2 +- contents/docs/error-tracking/alerts.mdx | 2 +- contents/docs/error-tracking/capture.mdx | 2 +- contents/docs/error-tracking/spikes.mdx | 2 +- contents/docs/error-tracking/stack-traces.mdx | 2 +- contents/docs/error-tracking/troubleshooting.mdx | 4 ++-- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx b/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx index 128172c27850..e23e47e9184d 100644 --- a/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx +++ b/contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx @@ -16,7 +16,7 @@ export const StepVerifySymbolSetsUpload: React.FC Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/alerts.mdx b/contents/docs/error-tracking/alerts.mdx index 6c594dbc68a6..13960379f00e 100644 --- a/contents/docs/error-tracking/alerts.mdx +++ b/contents/docs/error-tracking/alerts.mdx @@ -78,6 +78,6 @@ import { CalloutBox } from 'components/Docs/CalloutBox' - If you'd like a destination to be added that we don't yet support, [let us know in-app](https://app.posthog.com/project/2#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse). + If you'd like a destination to be added that we don't yet support, [let us know in-app](https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse). diff --git a/contents/docs/error-tracking/capture.mdx b/contents/docs/error-tracking/capture.mdx index fbf784c64237..73808930d383 100644 --- a/contents/docs/error-tracking/capture.mdx +++ b/contents/docs/error-tracking/capture.mdx @@ -28,7 +28,7 @@ import { CalloutBox } from 'components/Docs/CalloutBox' ### Automatic exception capture -If you followed one of our guides to [set up error tracking](/docs/error-tracking/installation) and you [enabled exception auto capture](https://app.posthog.com/project/2/error_tracking?activeTab=configuration), you'll have automatic exception capture enabled. +If you followed one of our guides to [set up error tracking](/docs/error-tracking/installation) and you [enabled exception auto capture](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture), you'll have automatic exception capture enabled. For browser SDKs (JavaScript Web, React, Next.js, etc.), you can configure which types of errors are automatically captured using the `capture_exceptions` option: diff --git a/contents/docs/error-tracking/spikes.mdx b/contents/docs/error-tracking/spikes.mdx index fe11554dfdd6..265d3c635d5a 100644 --- a/contents/docs/error-tracking/spikes.mdx +++ b/contents/docs/error-tracking/spikes.mdx @@ -25,7 +25,7 @@ If an issue is too new or hasn't had enough activity to establish a meaningful b ## Configuring spike detection -You can configure spike detection in the [error tracking configuration page](https://us.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-spike-detection). +You can configure spike detection in the [error tracking configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-spike-detection). -We strongly recommend you follow the [upload source maps](/docs/error-tracking/upload-source-maps) guide to ensure your stack traces are uploaded automatically in CI instead of manually debugging the process. If you're still having issues, [let us know in-app](https://us.posthog.com/project/2#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse). \ No newline at end of file +We strongly recommend you follow the [upload source maps](/docs/error-tracking/upload-source-maps) guide to ensure your stack traces are uploaded automatically in CI instead of manually debugging the process. If you're still having issues, [let us know in-app](https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse). \ No newline at end of file diff --git a/contents/docs/error-tracking/troubleshooting.mdx b/contents/docs/error-tracking/troubleshooting.mdx index 13e67986a70a..2f256576ad16 100644 --- a/contents/docs/error-tracking/troubleshooting.mdx +++ b/contents/docs/error-tracking/troubleshooting.mdx @@ -13,7 +13,7 @@ This page covers troubleshooting for Error Tracking. For setup, see the [install If PostHog isn't capturing errors: 1. Use the [SDK Doctor](/docs/sdk-doctor) to verify your SDKs are updated to the latest version -2. Verify **exception capture** is enabled in the [**Configuration** tab](https://app.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-exception-autocapture) in Error Tracking +2. Verify **exception capture** is enabled on the [**Configuration** page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture) in Error Tracking 3. Only unhandled exceptions auto-capture. For caught errors, use `posthog.captureException()`: ```js @@ -30,7 +30,7 @@ If PostHog isn't capturing errors: If stack traces show minified code instead of original source: -1. Verify source maps are uploaded to the correct project by navigating to [Error Tracking](https://app.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-symbol-sets). You'll see warnings for missing symbol sets +1. Verify source maps are uploaded to the correct project by navigating to [Error Tracking](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets). You'll see warnings for missing symbol sets 2. Source map paths must match your production bundle URLs exactly 3. Upload source maps *before* deploying code that references them From bfcc5c310edf7f33d5f419ddbf6392761006861c Mon Sep 17 00:00:00 2001 From: Christiaan Hendriksen Date: Wed, 15 Apr 2026 14:00:32 +0100 Subject: [PATCH 3/3] docs: sweep remaining error tracking links to new configuration route 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) --- contents/docs/error-tracking/_snippets/suppression-rules.mdx | 2 +- .../error-tracking/_snippets/web-install-error-tracking.mdx | 2 +- contents/docs/error-tracking/alerts.mdx | 2 +- contents/docs/error-tracking/assigning-issues.mdx | 2 +- contents/docs/error-tracking/grouping-issues.mdx | 2 +- contents/docs/error-tracking/pricing.mdx | 2 +- contents/docs/error-tracking/spikes.mdx | 2 +- contents/docs/error-tracking/stack-traces.mdx | 2 +- contents/docs/error-tracking/upload-source-maps/angular.mdx | 2 +- .../docs/error-tracking/upload-source-maps/github-actions.mdx | 2 +- contents/docs/error-tracking/upload-source-maps/nextjs.mdx | 2 +- contents/docs/error-tracking/upload-source-maps/nuxt.mdx | 3 +-- contents/docs/error-tracking/upload-source-maps/rollup.mdx | 2 +- contents/docs/error-tracking/upload-source-maps/vite.mdx | 2 +- contents/docs/error-tracking/upload-source-maps/webpack.mdx | 2 +- contents/tutorials/react-error-tracking.md | 2 +- 16 files changed, 16 insertions(+), 17 deletions(-) diff --git a/contents/docs/error-tracking/_snippets/suppression-rules.mdx b/contents/docs/error-tracking/_snippets/suppression-rules.mdx index 946a98d50ca3..16e714e7edb6 100644 --- a/contents/docs/error-tracking/_snippets/suppression-rules.mdx +++ b/contents/docs/error-tracking/_snippets/suppression-rules.mdx @@ -1,4 +1,4 @@ -Autocaptured exceptions can be ignored client-side by [configuring suppression rules](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-suppression-rules) in PostHog settings. You can only filter based on the exception type and message attributes because the stack of an exception may still be minified client-side. +Autocaptured exceptions can be ignored client-side by [configuring suppression rules](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-suppression-rules) in PostHog settings. You can only filter based on the exception type and message attributes because the stack of an exception may still be minified client-side. **Note:** A minimum SDK version of v1.207.8 is required, but we recommend keeping [up to date with the latest version](/docs/sdk-doctor) to ensure you have all of error tracking's features. -You can enable exception autocapture for the JavaScript Web SDK in the **Error tracking** section of [your project settings](https://us.posthog.com/settings/project-error-tracking#exception-autocapture). +You can enable exception autocapture for the JavaScript Web SDK on the [error tracking configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture). When enabled, this automatically captures `$exception` events by default for unhandled errors and unhandled promise rejections. You can fine-tune which errors are captured by passing a configuration object to `capture_exceptions`: diff --git a/contents/docs/error-tracking/alerts.mdx b/contents/docs/error-tracking/alerts.mdx index 13960379f00e..e15a7e24c5f6 100644 --- a/contents/docs/error-tracking/alerts.mdx +++ b/contents/docs/error-tracking/alerts.mdx @@ -6,7 +6,7 @@ To stay on top of issues, you can set up alerts. These enable you to post to Sla ## Issue created or reopened -To alert when an issue is created or reopened, go to [error tracking's configuration page](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-alerting) and click **Alerting**. This shows you a list of existing alerts. Clicking **New notification** brings you to a page to create a new one. +To alert when an issue is created or reopened, go to [error tracking's configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-alerting) and click **Alerting**. This shows you a list of existing alerts. Clicking **New notification** brings you to a page to create a new one. -To create a **custom grouping rule** in the [error tracking settings](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-custom-grouping): +To create a **custom grouping rule** in the [error tracking settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-custom-grouping): 1. Click the **Add rule** button to create a new grouping rule. 2. Select **Any** to match any of the criteria, or **All** to match all of the criteria. diff --git a/contents/docs/error-tracking/pricing.mdx b/contents/docs/error-tracking/pricing.mdx index e175524958c9..650e8b9f400f 100644 --- a/contents/docs/error-tracking/pricing.mdx +++ b/contents/docs/error-tracking/pricing.mdx @@ -48,7 +48,7 @@ By default, we capture all unhandled errors and rejections. This can capture mor } ``` -Alternatively, you can disable exception autocapture completely in your [project settings](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-exception-autocapture). +Alternatively, you can disable exception autocapture completely in your [project settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture). ### Suppression rules diff --git a/contents/docs/error-tracking/spikes.mdx b/contents/docs/error-tracking/spikes.mdx index 265d3c635d5a..3bf0001083f6 100644 --- a/contents/docs/error-tracking/spikes.mdx +++ b/contents/docs/error-tracking/spikes.mdx @@ -44,4 +44,4 @@ The following options are available: ## Getting notified about spikes -You can set up alerts to be notified when a spike occurs. Head to the [alerts tab](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-spike-detection) to configure notifications to Slack, Discord, Teams, HTTP Webhook and more +You can set up alerts to be notified when a spike occurs. Head to the [alerts tab](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-spike-detection) to configure notifications to Slack, Discord, Teams, HTTP Webhook and more diff --git a/contents/docs/error-tracking/stack-traces.mdx b/contents/docs/error-tracking/stack-traces.mdx index 405d50836394..d72f60faff03 100644 --- a/contents/docs/error-tracking/stack-traces.mdx +++ b/contents/docs/error-tracking/stack-traces.mdx @@ -61,7 +61,7 @@ Compiled or minified languages requires additional information to perform a proc The `source` of a frame in the exception stack trace should point to the minified code of your application which should contain the `sourceMappingUrl` parameter denoting the location of the source map. These files must either be publicly accessible for PostHog to fetch or uploaded manually to symbolify the stack trace. -You can see the symbol sets fetched by PostHog and the associated frames within the [error tracking settings](https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets). Any missing symbol sets will also be present along with the failure reason. From here, you can also manually upload missing symbol sets or replace existing ones. +You can see the symbol sets fetched by PostHog and the associated frames within the [error tracking settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets). Any missing symbol sets will also be present along with the failure reason. From here, you can also manually upload missing symbol sets or replace existing ones. + Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/upload-source-maps/github-actions.mdx b/contents/docs/error-tracking/upload-source-maps/github-actions.mdx index 2f32d7e9c27e..6b8c009b4c8b 100644 --- a/contents/docs/error-tracking/upload-source-maps/github-actions.mdx +++ b/contents/docs/error-tracking/upload-source-maps/github-actions.mdx @@ -77,7 +77,7 @@ We recommend storing `project-id` and `api-key` in GitHub Secrets (for example, 1. Confirm symbol sets are present in PostHog after the workflow runs. - + Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/upload-source-maps/nextjs.mdx b/contents/docs/error-tracking/upload-source-maps/nextjs.mdx index 4fbfcb30366f..a1f6dfd634e4 100644 --- a/contents/docs/error-tracking/upload-source-maps/nextjs.mdx +++ b/contents/docs/error-tracking/upload-source-maps/nextjs.mdx @@ -72,7 +72,7 @@ Before proceeding, confirm that source maps are being generated by checking for
- + Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/upload-source-maps/nuxt.mdx b/contents/docs/error-tracking/upload-source-maps/nuxt.mdx index 3884a5c6b894..7f156552ca3c 100644 --- a/contents/docs/error-tracking/upload-source-maps/nuxt.mdx +++ b/contents/docs/error-tracking/upload-source-maps/nuxt.mdx @@ -5,7 +5,6 @@ showStepsToc: true import CLIDownload from '../_snippets/cli/download.mdx' import CLIAuthenticate from '../_snippets/cli/authenticate.mdx' -import StepVerifySymbolSetsUpload from '../_snippets/StepVerifySymbolSetsUpload' ## Nuxt v3.7 and above @@ -73,7 +72,7 @@ Before proceeding, confirm that source maps are being properly uploaded. You can verify the injection is successful by checking your `.mjs.map` source map files for `//# chunkId=` comments. Make sure to serve these injected files in production, PostHog will check for the `//# chunkId` comments to display the correct stack traces. - + Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/upload-source-maps/rollup.mdx b/contents/docs/error-tracking/upload-source-maps/rollup.mdx index 89a72f42fe82..906b7d6e2114 100644 --- a/contents/docs/error-tracking/upload-source-maps/rollup.mdx +++ b/contents/docs/error-tracking/upload-source-maps/rollup.mdx @@ -61,7 +61,7 @@ showStepsToc: true
- + Check symbol sets in PostHog diff --git a/contents/docs/error-tracking/upload-source-maps/vite.mdx b/contents/docs/error-tracking/upload-source-maps/vite.mdx index 422e2792050f..0af1a738045a 100644 --- a/contents/docs/error-tracking/upload-source-maps/vite.mdx +++ b/contents/docs/error-tracking/upload-source-maps/vite.mdx @@ -64,7 +64,7 @@ Add these environment variables to your CI/CD service's project settings to auto Confirm source maps were successfully uploaded: -1. Go to your [symbol sets in PostHog](https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets) and verify your latest upload appears. +1. Go to your [symbol sets in PostHog](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets) and verify your latest upload appears. 2. Check your production JavaScript files in browser dev tools. They should include a source map reference comment: diff --git a/contents/docs/error-tracking/upload-source-maps/webpack.mdx b/contents/docs/error-tracking/upload-source-maps/webpack.mdx index a1c4a953d62f..1a66b8ffd8ed 100644 --- a/contents/docs/error-tracking/upload-source-maps/webpack.mdx +++ b/contents/docs/error-tracking/upload-source-maps/webpack.mdx @@ -57,7 +57,7 @@ showStepsToc: true
- + Check symbol sets in PostHog diff --git a/contents/tutorials/react-error-tracking.md b/contents/tutorials/react-error-tracking.md index 044a2e7af350..a8f3ad0f2a9b 100644 --- a/contents/tutorials/react-error-tracking.md +++ b/contents/tutorials/react-error-tracking.md @@ -72,7 +72,7 @@ Next, we'll set up PostHog to capture these errors. First, we need to install `p npm install posthog-js @posthog/react ``` -Next, create a `PostHogProvider.jsx` file in your `src` directory, and in it, initialize PostHog using your project token and host from [your project settings](https://app.posthog.com/settings/project). While you are there, make sure that [exception autocapture](https://app.posthog.com/settings/environment-error-tracking#error-tracking-exception-autocapture) is enabled. +Next, create a `PostHogProvider.jsx` file in your `src` directory, and in it, initialize PostHog using your project token and host from [your project settings](https://app.posthog.com/settings/project). While you are there, make sure that [exception autocapture](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture) is enabled. ```js // src/PostHogProvider.jsx