getsentry / getsentry/sentry-javascript

Allow filtering errors from host-environment SDKs

未关闭
#15,321 17 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看
Feature
主要语言
TypeScript
星标
8.7k
派生
1.8k
平均合并
1 天 17 小时
30 天内合并 PR
523

描述

### Problem Statement

Our site frequently gets embedded into other peoples apps (Facebook, TikTok, Afterpay, Klarna, etc) via them doing their own "in-app browser" type thing. This means our code is running in whatever javascript environment they have set, and we have little control of some of the code that gets injected into the page, same as a browser extension does.

Unlike a browser extension, these aren't filtered out by Sentry's wonderful issue filters and just fill our javascript issue tracking with unsolvable noise.

For example:

![Image](https://github.com/user-attachments/assets/49f744dd-7d1c-4a28-ab31-532de85b8f06)

![Image](https://github.com/user-attachments/assets/1ed4bdd8-890b-4d5b-8415-fe6f6a65a017)

![Image](https://github.com/user-attachments/assets/5ef20363-11f4-4dcf-af4d-8bcf2372b12e)

These are almost certainly coming from https://www.fillr.com/ which is embedded into the Afterpay mobile app, per the user agent: `Mozilla/5.0 (Linux; Android 14; SM-S918B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Mobile Safari/537.36 AfterpayMobile/5520`

### Solution Brainstorm

Similar to "filter issues from known extensions", add a "filter issues from known embedders" feature which uses that magic ( i assume you look for extension IDs in backtraces? ) but does some other magic for this use case instead. Not really idea what that magic would be sorry, real PITA.

### Product Area

Ingestion and Filtering

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。