Open keradus opened 3 years ago
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
@markstory is this being considered (so we should add "Status: On Hold") or we are unlikely to attend?
I would appreciate your decision whether the feature request makes sense ;)
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).
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.
@markstory is there an epic or some docs we can read regarding the evolution of the inbound filters?
@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.
thanks for the news, @jan-auer !
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.
+1. This would indeed be a handy feature 🙌
This would also be very handy for us!
We would really love to see that feature implemented! ❤️
+1 very important feature
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.
Any chance this feature will be implemented in foreseen future?
This would be useful for my product too.
Routing to @getsentry/product-owners-issues for triage ⏲️
Moved this to Issues, though maybe Settings - Relay is a better home?
I would also very much appreciate this. It would help to filter out all errors for a certain env during a maintenance which currently is quite a pain.
+1, would love to have this feature! We have test servers that we spin up sometimes and it'd be great to have the ability to filter out events from those before they hit the Sentry inbox (we currently can only identify them using tags).
This would be a great feature! For my use case, I have some events coming from a library that I don't have much control over (thus can't filter in my user level code), and only the tag has meaningful content for filtering (the title is pretty generic).
+1
I'm also interested on this.
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)