Description
Problem Statement
Sentry SDKs wrap user land code, and this can show up in the stack trace which is shown in Sentry. It is a confusing signal, which misleads developers to think the Sentry SDK was involved in the error.
Solution Brainstorm
We "beautify" stack traces in many ways already. Let's remove this in the default product view as well. It can be something the user can toggle on and off they like.
If it is not possible to "beuatify" this, or when toggled on there should be an info bubble on such stack frames which explains why the Sentry SDK is there and that there is no concern.
Product Area
Issues
Metadata
Metadata
Assignees
Type
Projects
Status
No status
Milestone
Relationships
Development
No branches or pull requests
Activity
getsantry commentedon Feb 14, 2025
Routing to @getsentry/product-owners-issues for triage ⏲️
scttcper commentedon Feb 14, 2025
@smeubank would be looking for just sentry/browser frames or is there another pattern we should filter out that would be safe?
smeubank commentedon Feb 17, 2025
Also sentry/node, but I will also check with the team
Lms24 commentedon Feb 17, 2025
for JS, I'd say we should probably match all
@sentry/*
packages. Most importantly though@sentry/(core|node|browser)
which is where instrumentation that causes this lives.