Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability able to filter events based off conditional logic around releases #77831

Closed
sentryadam0000345 opened this issue Sep 19, 2024 · 6 comments

Comments

@sentryadam0000345
Copy link

sentryadam0000345 commented Sep 19, 2024

Problem Statement

Based off existing Github issues, listed here:
#72932, #71901, #63132

Wanted to add one more feature request regarding our Inbound Filters.

Is there a way to set up an inbound filter than will drop errors events for releases below a certain number? Right now it looks like I can filter via glob matching but I'd like to be able to say something like "drop error events for all releases below x.x.x", ideally being able to filter out error events more than x releases behind current

Solution Brainstorm

Since this doesn't seem possible could we allow this functionality via an API? Even if it is more of an unsupported internal API, being able to set this functionality programmatically would be great.

Product Area

Settings - Projects

@getsantry
Copy link
Contributor

getsantry bot commented Sep 19, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Sep 20, 2024

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

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 3 Sep 20, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Sep 25, 2024

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

@jjbayer
Copy link
Member

jjbayer commented Sep 26, 2024

This should be relatively straight forward with Generic Inbound Filters if we extend the Getter impl of Event to support string access to "virtual" fields "release.version.major", etc.

@cmanallen
Copy link
Member

@zsperske
Copy link

I don't think this should have been closed? What in those docs solves the problem I described?

@github-actions github-actions bot locked and limited conversation to collaborators Dec 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

6 participants