getsentry / getsentry/sentry

Remove Sentry SDK info from stack trace

Open
#85,233 5 comments 0 reactions 0 assignees View on GitHub
Component: Issues Feature javascript Product Area: Issues
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

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.

![Image](https://github.com/user-attachments/assets/8ec0b48a-35ce-46a8-908d-24d60c96993a)

### 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

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. Start by locating the stack-trace presentation logic for the Issues product and review how existing stack-trace beautification works. Done means Sentry SDK frames are hidden by default, with either a user toggle or an explanatory info bubble when they remain visible.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.