Update filtering for an issue directly from web UI
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
I have an application that takes several days to update. Often, a new issue will appear in this app. It spams our Sentry instance with over 500 occurrences a day. By the time we finish updating our app, the issue has already consumed a significant portion of our monthly budget.
We already have inbound filters in Sentry, which implies Sentry can process issues on the server side before they hit our monthly quota. Inbound filters don't support all fields that I have in my issue (like tags) and it also doesn't support combining multiple filters (so I could target the exact set of events).
### Solution Brainstorm
**Solution 1**
We should be able to directly update the sampling rate of the issue from the web UI itself. Here's a rough sketch to indicate what I'm proposing:

**Solution 2**
Sentry already has the grouping hash that it uses to club events together, as shown in this image:

Sentry should let us provide this grouping hash in the inbound filter. That way, we can target the specific Issue precisely (no need to write precise wildcards), as shown in this image (from the filters page: `https://.sentry.io/settings/projects//filters/data-filters/`)

### Product Area
Issues
Contributor guide
Assessment
This issue has not been assessed yet.