[inbound filters] Ability to combine conditions in custom inbound filters

[GaurangTandon]

Problem Statement

I often need to discard future events for an issue quickly because it is spamming our Sentry instance, and causing us to go over our limited project quota.

However, I would prefer to keep existing events as they are, so I can refer to them in the future (when implementing a bug fix for that issue).

I cannot update my application's code to update the beforeSend callback - for example - because 1. the updated app can take a few days to rollout to 100% users, and 2. some users don't update their app even if we have rolled it out from our side. So, by the time my beforeSend callback update will deploy, our Sentry instance would have already exhausted its project quota.

Solution Brainstorm

I need a way to discard future events for an issue, without deleting the existing events for that issue, from the Sentry Web UI.

Currently, in Sentry, I can "delete existing events", or I can "delete and discard future events". Judging by that it looks like just "discard future events" (my request) should be possible to implement on the server.

Product Area

Issues

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[lobsterkatie]

Hi, @GaurangTandon - It sounds like inbound filters might be what you want.

[GaurangTandon]

Are you referring to this? @lobsterkatie Is there a way for me to combine release and version number in the inbound filter. For example: release matching "1.2.3" and error starting with "TypeError: "?