sentry-module
sentry-module copied to clipboard
Sourcemap uploaded to sentry but not reflecting to stack trace
Sourcemaps uploaded to sentry to see more realistic stack trace but it's not working, please help somebody
here's my config
dsn: process.env.SENTRY_DSN,
publishRelease: {
include: [], // automatically set at publishing time to relevant paths for the bundles that were built
ignore: [
'node_modules',
'.nuxt/dist/client/img'
],
configFile: 'sentry.properties',
},
config: {
release: 'release-1.0.0'
},
sourceMapStyle: 'hidden-source-map',
disableServerSide: true,
environment: 'development'
}```
It's showing this kind of stack trace instead of showing real code
and files also uploaded to sentry
Try removing sourceMapStyle
option and include
from publishRelease
.
@rchl Thank you so much for response, is this config okay now!
sentry: {
dsn: process.env.SENTRY_DSN,
publishRelease: {
ignore: [
'node_modules',
'.nuxt/dist/client/img'
],
configFile: 'sentry.properties',
},
config: {
release: 'release-1.2.0'
},
disableServerSide: true,
environment: 'development'
},
Appears OK but you can remove ignore
since you are just repeating what the module sets by default.
@rchl But it still doesn't show actual source code 😕
but files are uploaded successfully
Not sure then.
- Does sentry show some error related to not being able to parse source maps in individual events?
- Does the artifact name start with a dash (
-
) in your case? I thought that it normally is tilde (~
). Maybe your other Nuxt config settings affect it.
Sentry is showing this one, but it's just because i didn't connect it with my github repo but i did write release version manually in config. NB: my sentry is self-hosted it's running in docker.
I don't think I'll be able to help more with the given amount of information. You can potentially ask on Sentry's Discord for help.
I already asked there while creating this
I'll close this now because we can't act on it without more information. We'll re-open if more information is provided.
If it still doesn't work for you then please provide:
- full log from "nuxt build" including the part that publishes the release
- the request data from the network request that is sent to Sentry when capturing the error
(if there are any sensitive information then you'd have to make sure to filter those out)