diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index 09f457ea2ecc6c..cf1e3db26ff2a2 100644 --- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx @@ -1,21 +1,17 @@ -Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps set up, you can either: +Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps setup, you can use our built-in sourcemaps debugger modal directly in the Sentry product, or follow the manual steps listed below. -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below +## Use the Sourcemaps Debugger Modal -## Use the Sentry CLI +Sentry provides a built-in sourcemaps debugger modal that you can access directly from the **Issue Details** page. This tool helps you understand why your source maps might not be working correctly. -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). +To use the debugger modal: -For example, "Event ID: c2ad049f": +1. Navigate to an issue in your Sentry project +2. Click on the **Issue Details** page +3. Look for the sourcemaps debugger option in the interface +4. The debugger will analyze your source maps and provide detailed information about any issues -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. +This is the recommended approach for troubleshooting source maps issues as it provides real-time analysis and doesn't require any CLI tools. diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx index e874398dfa449e..c6367fc262bf9f 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -269,30 +269,20 @@ Sentry.init({ If you followed all of the steps above but still have issues setting up source maps using the legacy method this section will try to help troubleshoot your setup. -To troubleshoot your source maps set up, you can either: +To troubleshoot your source maps setup, you can use our built-in sourcemaps debugger modal directly in the Sentry product, or follow the manual steps listed below. -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below +### Use the Sourcemaps Debugger Modal -### Use the Sentry CLI +Sentry provides a built-in sourcemaps debugger modal that you can access directly from the **Issue Details** page. This tool helps you understand why your source maps might not be working correctly. -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). +To use the debugger modal: - +1. Navigate to an issue in your Sentry project +2. Click on the **Issue Details** page +3. Look for the sourcemaps debugger option in the interface +4. The debugger will analyze your source maps and provide detailed information about any issues -The `sourcemaps explain` command requires an auth token with the following scopes: `project:admin`, `release:admin`, `event:read`, and `organization:read`. We recommend creating an [internal integration token](/organization/integrations/integration-platform/internal-integration/) over a personal token. - - - -For example, "Event ID: c2ad049f": - -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. +This is the recommended approach for troubleshooting source maps issues as it provides real-time analysis and doesn't require any CLI tools. diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 75a2729a7435e7..baf1699569c866 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -30,25 +30,20 @@ Dependency versions that require the legacy method of uploading source maps incl -Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps set up, you can either: +Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps setup, you can use our built-in sourcemaps debugger modal directly in the Sentry product, or follow the manual steps listed below. -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below +## Use the Sourcemaps Debugger Modal -## Use the CLI +Sentry provides a built-in sourcemaps debugger modal that you can access directly from the **Issue Details** page. This tool helps you understand why your source maps might not be working correctly. -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). +To use the debugger modal: -For example, "Event ID: c2ad049f": +1. Navigate to an issue in your Sentry project +2. Click on the **Issue Details** page +3. Look for the sourcemaps debugger option in the interface +4. The debugger will analyze your source maps and provide detailed information about any issues -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. -If it doesn't, let us know by filing an issue on our [Sentry CLI repo](https://github.com/getsentry/sentry-cli) so we can make it better. +This is the recommended approach for troubleshooting source maps issues as it provides real-time analysis and doesn't require any CLI tools. ## Follow Manual Steps