←back to thread

Et Tu, Grammarly?

(dbushell.com)
279 points dbushell | 2 comments | 29 Mar 25 10:27 UTC | HN request time: 0.417s | source
Show context
emptysea ◴[29 Mar 25 15:40 UTC] No.43516362[source]▶
At work we have a lot of sentry errors related to browser extensions doing weird stuff.

Chrome’s Google translate is also notorious for breaking react based sites.

It ends up being a tedious triage process to ignore each new extension issue. We use the client side filtering to reduce our ingest volume. In general we have to have a lot higher thresholds to handle the noise vs our backends.

replies(2): >>43516812 #>>43516871 #
1. jgalt212 ◴[29 Mar 25 16:48 UTC] No.43516812[source]▶
> At work we have a lot of sentry errors related to browser extensions doing weird stuff.

Are you referring to the "Object captured as exception" error which Sentry refuses to give any guidance on? We just end of filtering these out client-side.

replies(1): >>43517558 #
2. emptysea ◴[29 Mar 25 18:40 UTC] No.43517558[source]▶
Ah yeah I remember that one, but can’t remember the origin.

A lot of times the reason sentry can’t do much is because the browser JS VMs have terrible/non-existent stack traces, especially true with things like unhandled rejected promises.