Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add reason for in_app to frames #3672

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

sentrivana
Copy link
Contributor

@sentrivana sentrivana commented Oct 18, 2024

Sentry enhances the in_app decision from the SDK, sometimes overriding it.

In case the decision to set in_app to True comes from the user themselves (by setting in_app_include), we don't want Sentry to override it.

Currently there's no way for Sentry to know what led to the decision in the SDK. Changing that here.

Draft: To be clarified whether in_app_include_used should contain the actual prefix from the user's in_app_include or a general category like in_project_root, in_app_include outlining the general reason for marking it as in app.

Closes #3671

Sentry enhances the in_app decision from the SDK, sometimes overriding it.

In cases the decision to set in_app to True comes from the user themselves
(by setting in_app_include), we don't want Sentry to override the decision.
Currently there's no way for Sentry to know what led to the decision in the
SDK. Changing that here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Track when in_app_include is used
1 participant