Content
@
0 reply
0 recast
0 reaction
Colin
@colin
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?
4 replies
2 recasts
9 reactions
Tony D’Addeo
@deodad
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
1 reply
0 recast
3 reactions
jtgi
@jtgi
Following this and hoping for answers. My experience with sentry and rollbar: Because of the noise, these tools are not good for proactive alerting out of the box, only investigative/debugging, for ex: user 1 wrote in with some error, go lookup their user id in sentry.
1 reply
0 recast
3 reactions
timdaub
@timdaub.eth
Nothing
0 reply
0 recast
1 reaction
Damian
@zimmcognito
We have moved to https://trackjs.com/ and so far for many months this have been ongoing success for us
0 reply
0 recast
0 reaction
