Frontend

The vast majority of Sentry errors for our frontend are unrelated to our codebase and are instead related to random extensions/packages, making it very noisy.

We've been trying to blocklist certain packages/keywords but it's not scalable. 

What does everyone do for frontend error tracking?

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

Introduce an error class for application level errors

catch exceptions and wrap them with your application error (use cause so you can see original error) in important parts of your app

use custom fingerprinting so they group appropriately

now you can identify where users are running into problems

Building @warpcast and @farcaster, new dad, like making food

tldr it’s not about getting rid of the haystack just making sure the needles can be more easily found

that being said this really prevent the large number of irrelevant errors

just helps you find important ones and setup alerts on them if needed (though usually it’s easier to do this w backend monitoring)