getsentry / getsentry/sentry

Can't find bad/missing project setups

Open
#59,072 3 comments 0 reactions 1 assignee Claimed by @Dhrumil-Sentry View on GitHub
Product Area: Projects - Project Details Project
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

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

1. You are not seeing your data in Sentry because you have certain inbound filters enabled- Hydration errors, health check transactions or chunk-load errors
2. On the other hand, your issues are noisy because you are not filtering away errors from browser extensions for e.g.
3. You have terrible alert rules that send an alert 1000 times a day 😓
4. 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 https://github.com/getsentry/sentry/issues/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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.