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
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
jtgi
@jtgi
For proactive alerting, I only had good results whitelisting specific errors. And whenever I could I’d get from backend instead. Never made “increased errors” work well. Even after piping into datadog with anomaly detection.
0 reply
0 recast
1 reaction
