You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not always clear when a project has bad or missing setups that are sending junk data to Sentry or filtering away valuable data.
When developers try to triage problems - there's no way to know if something is awry with the setups itself.
Here are some examples:
You are not seeing your data in Sentry because you have certain inbound filters enabled- Hydration errors, health check transactions or chunk-load errors
On the other hand, your issues are noisy because you are not filtering away errors from browser extensions for e.g.
You have terrible alert rules that send an alert 1000 times a day 😓
You are not sending releases or other useful context to Sentry
This issue is a super issue meant to capture all such concerns and issues such as #57458
Please comment below to share more examples we should consider
Solution Brainstorm
On the project details page- we can surface setups that we know are incorrect or bad
Product Area
Settings - Projects
The text was updated successfully, but these errors were encountered:
Here's another example- Customers who want to use replays need to be on the SDK version that supports replays, how can we surface this information better to them?
Problem Statement
It's not always clear when a project has bad or missing setups that are sending junk data to Sentry or filtering away valuable data.
When developers try to triage problems - there's no way to know if something is awry with the setups itself.
Here are some examples:
This issue is a super issue meant to capture all such concerns and issues such as #57458
Please comment below to share more examples we should consider
Solution Brainstorm
On the project details page- we can surface setups that we know are incorrect or bad
Product Area
Settings - Projects
The text was updated successfully, but these errors were encountered: