Skip to content

docs(sourcemaps): Remove mentions of sentry-cli sourcemaps explain #15481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(sourcemaps): Remove mentions of sentry-cli sourcemaps explain #15481

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 1 addition & 18 deletions platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,4 @@
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:

1. Use our automated verification tool inside `sentry-cli`, or
2. Follow the manual steps listed below

## Use the Sentry CLI

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).

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.
Setting up source maps can be tricky, but it's worth it to get it right. You can follow the steps below to troubleshoot your source maps set up.

<PlatformSection notSupported={["javascript.electron"]}>

Expand Down
25 changes: 0 additions & 25 deletions platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,31 +267,6 @@ 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:

1. Use our automated verification tool inside `sentry-cli`, or
2. Follow the manual steps listed below

### Use the Sentry CLI

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).

<Alert title="Note" level="warning">

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.

</Alert>

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.

<PlatformSection notSupported={["javascript.electron"]}>

### Verify a release is configured in your SDK
Expand Down
22 changes: 2 additions & 20 deletions platform-includes/sourcemaps/troubleshooting/javascript.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,27 +30,9 @@ Dependency versions that require the legacy method of uploading source maps incl

</Alert>

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. You can follow the steps below to troubleshoot your source maps set up.

1. Use our automated verification tool inside `sentry-cli`, or
2. Follow the manual steps listed below

## Use the CLI

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).

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.
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.

## Follow Manual Steps
## Troubleshooting Steps

### Verify Artifacts Are Uploaded

Expand Down
Loading