getsentry / getsentry/sentry

Region-based inbound filtering

Open
#107,444 4 comments 0 reactions 0 assignees View on GitHub
Component: Inbound Filters Feature Product Area: Ingestion and Filtering
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

We have recurring bot traffic from non-operated regions that pollutes CFSR and other metrics. The current mitigation (IP-based filtering) is brittle, bots rotate IPs and teams are continually chasing new IPs to keep metrics clean. We need a safer, lower-maintenance way to exclude traffic from whole regions (country/geo) at ingestion time.

### Solution Brainstorm

_No response_

### Product Area

Unknown

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the ingestion path and existing IP-based filtering, then clarify how country or geo regions should be identified and configured. Done should mean an agreed, safer region-based filtering design with coverage for the relevant ingestion behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.