Add legacy Edge versions 12-18 to Inbound Data Filters

[mKlus]

Problem Statement

Edge versions 12-18 is obsoleted and has a limited javascript API functionality.
Many web apps/pages dropped support for Edge 12-18 and it would make sense to be able to setup a rule to ignore any errors coming from Edge 12-18 the same way we can ignore errors coming from Internet Explorer.

Solution Brainstorm

No response

[mKlus]

Thinking about this bit more, I wonder if that should be extended to all browsers so we have an ability to filter out errors from unsupported browsers, including older versions of Chrome, Firefox etc.

[getsentry-release]

Routing to @getsentry/owners-ingest for triage. ⏲️

[untitaker]

Thanks, I have added this to our backlog. It may be that this feature generally needs to become more flexible to adapt to browsers becoming outdated over time.

[mKlus]

Hi @untitaker, thanks for adding this to the backlog. Do you have an approximate time when this could be released?

[untitaker]

Sorry, no. I can only say that your feedback has been recorded, we can't commit to working on it yet.

[mKlus]

Thanks @untitaker. Is there any work around that you would recommend?

[untitaker]

There's not a whole lot you can do on the serverside at the moment, but you could disable the SDK on the clientside if the useragent is bad/old?

[jitendravyas]

Please do this for firefox too https://twitter.com/jitendravyas/status/1549701901088079873

[mscuthbert]

This would be very helpful for one of my projects which does a lot with modern WebAudio and our issues reports get clogged with people ignoring the BrowserUpdate notifications saying that it won't work for them and continuing into the site.

(If you're looking for a syntax to use, the BrowserUpdate configuration is well known and many people will be able to adopt it directly. Though you'll probably want a much more permissive default than they use).

(Adding OS filtering as well would also let me filter out a notorious web crawler that crashes on all modern JS and reports Safari 10.0 on Linux, which doesn't exist)

[johannesnagl]

same here: i think this would be super helpful. we would definitely need some additional rules here:

as mentioned in #54934, specifying a browserslist would make a lot of sense.

[hubertdeng123]

Removing Waiting for: Product Owner since it looks like it is on the backlog of Telemetry Experience