Echo JS 0.11.0

<~>
jylauril 3911 days ago. link 2 points
Generally I think it's a bad idea to use Google Analytics for JS error tracking, but I can see why someone would want to do that... kind of. The downside of doing it this way is that you can't group the errors in any way and you can't have proper stacktraces with the error events.

Also from my experience of running high-traffic sites, 95% of the JavaScript errors we capture are caused by different browser extensions/addons and anti-virus/spam filters, which can render the whole error tracking completely useless if you don't have the right tools to identify patterns, etc. And for that, Google Analytics really is not the way to go.

If you have a high-traffic site, you should really invest into some other tool than GA. Qbaka (https://qbaka.com) or Bugsnag (https://bugsnag.com) are really good and affordable. (No, I don't have any affiliation with either of those.)

Replies