-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Conditionally send View Hierarchies to Sentry with certain events #47108
Comments
Assigning to @getsentry/support for routing, due by Monday, April 10th at 5:00 pm (sfo). ⏲️ |
Routing to @getsentry/team-mobile for triage, due by Wednesday, April 12th at 10:27 am (sfo). ⏲️ |
The user should be able to adjust this in |
They have to use the hints in |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
@michaelchai-sentry which platform does the user have set up? |
On Cocoa this problem will be solved with getsentry/sentry-cocoa#3007 |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Other platforms already support the filtering of view hierarchies and screenshots via |
Problem Statement
A user reported that they would only like to send View Hierarchies for events of a certain level (i.e. only fatal events). Right now, it is a opt-in feature that allow only allows you to set it to true/false. The reasoning behind wanting this is to reduce the overhead of data sent, and that they want to cut down the noise and are only interested in View Hierarchies for certain events.
Solution Brainstorm
Add some conditional logic to this feature, such as the before send callback
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: