improve inbound filters

[Niryo]

Problem Statement

In mobile, we have many requests that are coming from outdated clients, and it makes it hard to understand which errors are not relevant anymore (we keep getting errors that were already fixed in newer clients).
Our current way of overcoming this issue is to use inbound filters to filter out versions from old clients. The issue with that approach is that inbound filters are matched as strings, and we can't add filters like this for example: > 2.100155.0, in order to filter out all releases that are less than version 2.100155.0.
So in order to achieve something like that, we have some complex inbound filters that we update on every new release, and it looks like this:
com.app@2.?.+
com.app@2.??.+
com.app@2.???.+
com.app@2.????.+
com.app@2.?????.+
com.app@[0-1].??????.?+*
[email protected]?????.?+*
[email protected]??.?+*
[email protected][0-4]?.?+*
[email protected][0-4].?+*

Not pleasant at all as you can see.

Solution Brainstorm

One suggested solution would be to support reacher filter syntax, like suggested above.
Another option is to add whiteList filters instead of blacklist, so we could just say "filter out everything which isn't coming from this release and that release.

Product Area

Ingestion and Filtering

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-ingestion-and-filtering for triage ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[jangjodi]

Thank you for the suggestion! I have added this to our backlog, though I am unsure when this can be prioritized.

[Dav1dde]

Would an inverted glob pattern already solve this for you?
E.g. a syntax like [email protected] filtering everything except the version [email protected].

I know this is still far from a good user experience and not a solution (especially that this does not match well with multiple rules), but it may make configuring the filter a bit easier for your usecase.