Inbound Filters by tags

[keradus]

hey, it would be great to have a way to set up Inbound Filters based on value of tags - eg to drop all incoming events from given user (I know it's doable now with IP, yet many users can share single IP)

┆Issue is synchronized with this Jira Improvement by Unito

[BYK]

@markstory is this being considered (so we should add "Status: On Hold") or we are unlikely to attend?

[keradus]

I would appreciate your decision whether the feature request makes sense ;)

[shadow-cs]

I'd find that extremely useful indeed. I'd like to filter devices (we use Sentry in an IoT world) based on a serial number if one goes haywire (since the devices are usually behind cell operator gateway, IP filtering won't do us much good in this case).

[markstory]

I'm not overly close to the roadmap for inbound filters. There is a team working on evolving inbound filters but tags are not currently part of that scope either.

[shadow-cs]

@markstory is there an epic or some docs we can read regarding the evolution of the inbound filters?

[jan-auer]

@shadow-cs We can't share a public roadmap on inbound filters just yet. Most likely, I can share something in summer.
Controlling traffic by tags is definitely on our radar.

[keradus]

thanks for the news, @jan-auer !

[watzon]

I agree that this would make a fantastic addition. Would PRs be welcome? I might be willing to get my hands dirty if it could speed things up.

[parichay28]

+1. This would indeed be a handy feature 🙌

[jlaz-globality]

This would also be very handy for us!

[phellmayr1]

We would really love to see that feature implemented! ❤️

[mhuebner]

+1 very important feature

[jarrodlombardo-EventBase]

We have some clients hang on to old versions of our apps for many months and not being able to filter by tags eats up 100-200k events from our quota every month. Please implement this.

[cytivrat]

Any chance this feature will be implemented in foreseen future?

[Edgar-Cordova]

This would be useful for my product too.

[ericriff]

I'm also interested on this.

[AntSworD]

I'm also interested on this.

[rachrwang]

Hi everyone - thank you for sharing your interest in this ticket. We don't have immediate plans to work on this, though it's very helpful for future prioritization discussions.

[keradus]

very unfortunate msg after 4 years of waiting

[Angelodaniel]

Hey I've been thinking about this recently @keradus
There is a way to do it:

• Change the fingerprint rules to supergroup all issues with Tag X into 1 issue
• Delete and Discard that Issue.
  That will group issues with Tag X into 1 issue and delete them based on the fingerprint value.

It's not a direct filter on Tags, but rather a workaround to do this.
For the rest of the people in the thread, it could also be on other fields than just tags -> https://docs.sentry.io/concepts/data-management/event-grouping/fingerprint-rules/
Let me know if that would help

[keradus]

@Angelodaniel , would that help with preventing those events to be consumed at all? or only remove already consumed events? (but allow them to be reported again)

remember I want to filter them out in a way like they were never sent and that they do not consume any quota/limits

Inbound Data Filters
Filters allow you to prevent Sentry from storing events in certain situations. Filtered events are tracked separately from rate limits, and do not apply to any project quotas.

[lobsterkatie]

Delete and discard means you never see them again. Keep in mind it's only available on the Business plan, though.