From b3ccf6c59ad19ded0fda95a2c3194693e84d7c34 Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Fri, 8 Nov 2024 10:08:59 +0100 Subject: [PATCH 1/4] Recommend to check `symbolicator` if source maps are not working on Self-Hosted --- .../legacy-troubleshooting/javascript.mdx | 7 ++++++- .../legacy-uploading-methods/javascript.mdx | 13 +++++++------ .../sourcemaps/troubleshooting/javascript.mdx | 7 ++++++- 3 files changed, 19 insertions(+), 8 deletions(-) diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index 1e198d189a1bb..302500be2ea83 100644 --- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx @@ -239,7 +239,12 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e If you're hosting your source maps publicly, make sure you have the "Enable JavaScript source fetching" option activated under **[Settings] > Projects > Select your project > General Settings**. -## Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker) +## (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally + +If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. +You can do so by checking the container's logs. + +## (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk. diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx index 0dea289bd824f..0b1b66e80cc00 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -73,8 +73,8 @@ export default defineConfig({ ], }); ``` - + ## Uploading using Sentry Webpack Plugin Version 1.x @@ -82,7 +82,6 @@ Assuming you have the `@sentry/webpack` package installed on version `1.x`, you Example: - ```javascript {filename:webpack.config.js} const SentryWebpackPlugin = require("@sentry/webpack-plugin"); @@ -111,7 +110,6 @@ module.exports = { The Sentry webpack plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly: - ```javascript Sentry.init({ dsn: "___PUBLIC_DSN___", @@ -136,7 +134,6 @@ This applies when using the following packages on version `2.x` and above: Example of using the `release.uploadLegacySourcemaps` option: - ```javascript {filename:webpack.config.js} {tabTitle:Webpack} const { sentryWebpackPlugin } = require("@sentry/webpack-plugin"); @@ -251,7 +248,6 @@ export default { The Sentry bundler plugins will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release.name` option exactly: - ```javascript Sentry.init({ dsn: "___PUBLIC_DSN___", @@ -506,7 +502,12 @@ If you are using `sentry-cli` to upload your artifacts, starting with version `2 Sometimes build scripts and plugins produce pre-compressed minified files (for example, webpack's [compression plugin](https://github.com/webpack/compression-webpack-plugin)). In these cases, you'll need to disable such plugins and perform the compression **after** the generated source maps/source files have been uploaded to Sentry. -### Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker) +### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally + +If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. +You can do so by checking the container's logs. + +### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk. diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 9e44e55413939..0c4523246eda2 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -166,10 +166,15 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e ### Verify Source Fetching is Enabled If you're hosting your source maps publicly, make sure you have the "Enable JavaScript source fetching" option activated under **[Settings] > Projects > Select your project > General Settings**. + +### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally + +If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. +You can do so by checking the container's logs. -### Verify Workers Are Sharing Same Volume as Web (if running self-hosted Sentry via Docker) +### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk. From 8dae3f33ecbc76299dbe53953518642ec3b73929 Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Tue, 12 Nov 2024 09:41:28 +0100 Subject: [PATCH 2/4] Update platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx Co-authored-by: Liza Mock --- .../sourcemaps/legacy-troubleshooting/javascript.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index 302500be2ea83..5532da0544032 100644 --- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx @@ -241,8 +241,7 @@ If you're hosting you ## (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally -If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. -You can do so by checking the container's logs. +If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs. ## (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web From e9d4a4b3a5ef923a66a1f4e7cf8d26bc7bd6f455 Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Tue, 12 Nov 2024 09:41:34 +0100 Subject: [PATCH 3/4] Update platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx Co-authored-by: Liza Mock --- .../sourcemaps/legacy-uploading-methods/javascript.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx index 0b1b66e80cc00..02e4c0f7d8b9d 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -504,8 +504,7 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e ### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally -If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. -You can do so by checking the container's logs. +If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs. ### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web From ddd04a39b15bcd48d6201f146c86f6c2d13f754b Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Tue, 12 Nov 2024 09:41:51 +0100 Subject: [PATCH 4/4] Update platform-includes/sourcemaps/troubleshooting/javascript.mdx Co-authored-by: Liza Mock --- platform-includes/sourcemaps/troubleshooting/javascript.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 0c4523246eda2..d3ea061c16359 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -171,8 +171,7 @@ If you're hosting you ### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally -If you are running a self-hosted version of Sentry, verify that the `symbolicator` service/container is operating normally. -You can do so by checking the container's logs. +If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs. ### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web