Repository navigation
Source Map Upload *summary* #712
Description
Problem Statement
Today, when configuring the verbosity of my withSentryConfig(), it seems like I have two options for logging what's going on with source maps:
silent:true-> no evidence of source maps working at allsilent:false-> hundreds of lines of output.
Solution Brainstorm
Here's an example of what we see today:
getsentry/sentry-javascript#20 49.36 > Found 252 files
getsentry/sentry-javascript#20 49.39 > Analyzing 252 sources
getsentry/sentry-javascript#20 49.44 > Adding source map references
getsentry/sentry-javascript#20 51.08 > Bundled 252 files for upload
getsentry/sentry-javascript#20 51.08 > Bundle ID: 66b7d9d0-08a0-58e1-9a72-1cb685c7d9e8
getsentry/sentry-javascript#20 52.34 > Uploaded files to Sentry
getsentry/sentry-javascript#20 52.49 > File upload complete (processing pending on server)
getsentry/sentry-javascript#20 52.49 > Organization: my-org
getsentry/sentry-javascript#20 52.49 > Project: my-proj
getsentry/sentry-javascript#20 52.49 > Release: my-release-123
getsentry/sentry-javascript#20 52.49 > Dist: None
getsentry/sentry-javascript#20 52.49 > Upload type: artifact bundle
getsentry/sentry-javascript#20 52.49
getsentry/sentry-javascript#20 52.49 Source Map Upload Report
getsentry/sentry-javascript#20 52.49 Scripts
getsentry/sentry-javascript#20 52.49 ~/007f03f0-75b6-4f4e-af77-5229486f1559-70.js (sourcemap at 2829.js.map, debug id 007f03f0-75b6-4f4e-af77-5229486f1559)
getsentry/sentry-javascript#20 52.49 ~/0255c949-852e-4016-9049-b6646eb02e71-96.js (sourcemap at 6684.js.map, debug id 0255c949-852e-4016-9049-b6646eb02e71)
getsentry/sentry-javascript#20 52.49 ~/0366c355-39c2-4b90-a7be-5f8e6671916b-26.js (sourcemap at page.js.map, debug id 0366c355-39c2-4b90-a7be-5f8e6671916b)
getsentry/sentry-javascript#20 52.49 ~/084f15e6-c388-4f5c-a173-1e532bc5be45-51.js (sourcemap at page.js.map, debug id 084f15e6-c388-4f5c-a173-1e532bc5be45)
( ... and hundreds of lines more )
It's also a little confusing that there are three separate upload steps. (edge/client/node?)
Ideally, I'd like the tools to default to a reasonable amount of logging, telling me the basics of what's going on without listing every single file. Maybe something like this:
Sentry source map upload (node.js): 252 files uploaded for release my-release-123
Sentry source map upload (edge): 258 files uploaded for release my-release-123
Sentry source map upload (client): 228 files uploaded for release my-release-123
Am I missing something? Is there a good way to get a reasonable amount of verbosity with today's tools?
Activity
lforst commentedon Mar 31, 2025
That is an extremely reasonable ask. @szokeasaurusrex can we somehow add a structured output to the JS layer of the CLI?
Lms24 commentedon Mar 31, 2025
Agreed, this sounds very reasonable and it's not the first time we're getting requests around logs. I just transferred the issue to our bundler plugins repo because this needs to be addressed in our plugins once the CLI allows us to do so.
szokeasaurusrex commentedon Mar 31, 2025
@lforst by structured output do you mean like a JSON output?
We can probably add it, only question is how difficult it will be to implement. Will need to investigate that more thoroughly
lforst commentedon Apr 15, 2025
yes json output would be great
tomastan commentedon Jun 3, 2025
Let me be that +1.
We also have so many lines in output it pushes other important output out of screen buffer on terminals. Make it
silent: trueis too radical as well, as we don't see if Sentry sourcemaps are even enabled in that specific env. My recommendation would be: just to let control the verbosity. An option for a summary like "X sourcemaps were uploaded to Sentry", would be perfect for our cases