How do source maps work with a Sentry SDK pointed at Bicho? #65
|
Can Bicho map minified JavaScript stacks from Sentry events? Is changing the DSN or redirecting a Sentry artifact uploader sufficient? |
Replies: 1 comment
|
Bicho can enrich JavaScript frames when the captured Sentry event supplies matching debug IDs and generated positions. A release label, bundle filename, or DSN change alone does not enable mapping. Your build tooling and SDK must emit the linkage. Upload the matching Source Map v3 JSON through Bicho's authenticated A captured frame can carry Bicho does not accept Sentry artifact-bundle uploads, fetch remote maps, discover Documentation - Source maps Documentation - Move from Sentry |
Bicho can enrich JavaScript frames when the captured Sentry event supplies matching debug IDs and generated positions. A release label, bundle filename, or DSN change alone does not enable mapping. Your build tooling and SDK must emit the linkage.
Upload the matching Source Map v3 JSON through Bicho's authenticated
PUT /api/:project_id/sourcemaps/:debug_idendpoint. Use the admin bearer token for uploads, never the SDK ingest key. Maps are immutable within a project/debug ID: identical normalized content can be retried, but changed content returns 409.A captured frame can carry
debug_iddirectly. Alternatively,debug_meta.imagescan associate atype: "sourcemap"entry'sdebug_idwith an …