getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
37.47k stars 4.03k forks source link

Unable to get Source Maps working with Debug ID #73511

Open baubie opened 2 days ago

baubie commented 2 days ago

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

What are you trying to accomplish?

Trying to get source maps to work with an internal Vue app with self-hosted Sentry. We are on the latest version of Sentry, Webpack Plugin, and Vue Sentry SDK as of this morning (June 28).

How are you getting stuck?

We are using the sentryWebpackPlugin to upload source maps. Debug IDs are set, they are being sent with errors, source artifacts are uploaded, but nothing is working.

image

Clicking on Unminify Code it tells us everything looks good: image

Looking at the raw event JSON we see the debug_meta field:

"debug_meta":{"images":[{"code_file":"http://localhost/static/js/app.43e39073ab510c561674.js","debug_id":"1b48b47e-183c-4028-b5e5-d1bef3ec7bed","type":"sourcemap"}]},"environment":"production","errors":[{"type":"js_no_source","symbolicator_type":"missing_source","url":"http://localhost/static/js/app.43e39073ab510c561674.js"}

Uploading the source map says it was fine: image image

In out WebPack config we have:

  devtool: 'source-map' ,
  output: {
    path: config.build.assetsRoot,
    filename: utils.assetsPath('js/[name].[chunkhash].js'),
    chunkFilename: utils.assetsPath('js/[id].[chunkhash].js'),
    sourceMapFilename: '[file].map',
  },

The debug ID of 1b48b47e... seems to match up to the source/maps being uploaded.

Where in the product are you?

Issues - Source Maps

Link

No response

DSN

No response

Version

24.6.0

getsantry[bot] commented 2 days ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 2 days ago

Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️

lforst commented 1 hour ago

Hi, the Unminify Code button tells you:

You completed all of the steps above. Capture a new event to verify your setup!

Have you sent a new event and selected "latest" in the issues view?

If yes, and it is still broken, please check the logs of the symbolicator service in your self-hosted instance.