search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.93k stars 4.18k forks source link

Add the ability to filter events for versions 'less than' a specific version in the inbound filter #43941

Open PhilHannent opened 1 year ago

PhilHannent commented 1 year ago

Problem Statement

A custom filter for a given text string is a risky addition to add as you are blocking the ability to detect regressions. It would be better to filter out older versions of the software from bug reports. The existing filter only support glob matching, however this would then mean that with each release of the software we need to append the older version to that list. The list would then become very long and need to be maintained.

https://docs.sentry.io/product/data-management-settings/filtering/

Solution Brainstorm

My initial thought would be that rather than glob, there needs to be a filter where we can ignore versions less than a certain release. For example: < 7.7.8

It might also be nice to have an API endpoint which we can put into our CI/CD system which would update the field of the current release version.

The added complexity is that release channels would have a different filter. A beta channel could be on v7.8.0 whereas a production would still be on 7.7.10. Developers would want to see both.

Perhaps a simpler solution would be a switch which when on only allowed the most recent version of that channels bugs.

getsantry[bot] commented 1 year ago

Assigning to @getsentry/support for routing, due by (yyz). ⏲️

getsantry[bot] commented 1 year ago

Routing to @getsentry/workflow for triage, due by (sfo). ⏲️

scttcper commented 1 year ago

@PhilHannent we've heard that people want more options when filtering by releases. Eg "last 2 releases". Which part of the product specifically are you referring to? Alerts? Issue search? Thanks!

Edit: i think setting the "active" version manually also isn't something we support, but I'd be interested to know if the "active" release is working for your use case.

PhilHannent commented 1 year ago

This issue came up due to the addition of attachments in our Qt/C++ integration. Previously, we had an in house system and we had a constant for a version we didn't care about (so we could see the previous couple of versions).

However, we are looking to be more forceful with getting users to upgrade to the latest version, so anything less than what is in the production release is not worth spending time on. I appreciate we might miss problems, but statistically, if the problem hasn't been fixed it will turn up in the latest eventually.

A big factor for us turning on alerts is the signal to noise ratio, we really want to keep the noise down, so that developers are notified of something truly new and especially to jump on problems in a new release.

github-actions[bot] commented 1 year 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: Backlog or Status: In Progress, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

meotimdihia commented 11 months ago

Yes, it is weird, Sentry should have this feature. Events that do not belong to the latest version should be filtered The browsers always cache the old version, old events are still sent for days.