Skip to content

feat(inbound-filters): Add an operator to custom filter conditions - #127374

Open
shellmayr wants to merge 1 commit into
masterfrom
shellmayr/feat/inbound-filter-condition-operators
Open

shellmayr wants to merge 1 commit into
masterfrom
shellmayr/feat/inbound-filter-condition-operators

Conversation

@shellmayr

Copy link
Copy Markdown
Member

A custom inbound filter condition could only match its values. Give each
condition an operator: matches, does_not_match, or a version comparison
(gt, gte, lt, lte) on release. The operator defaults to matches, so a
condition stored before the field existed keeps its meaning and reads
back as matches.

does_not_match compiles to Relay as "the field is present and does not
match". Relay reads a missing field as no match, so a bare not would drop
every event without a release or a client IP.

A comparison compiles to Relay's release rule condition, which needs
sentry-relay 0.10.1. The API only accepts it on release, with exactly one
value that parses as a release with a version, since Relay never matches
a comparison against a commit hash or a glob.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 14, 2026
@shellmayr
shellmayr marked this pull request as ready for review October 14, 2026 14:23
@shellmayr
shellmayr requested review from a team as code owners October 14, 2026 14:23

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants