Cornell continues their series on using TrackJS by showing how they filter out noisy, unactionable errors from their reports.

The fact that it happened in Mac OS X and Safari, but not any other browser, is a sign something might be amiss with a plugin. If you plugin in that nasty function name into Google, you get almost no hits. Well … if it isn’t in your code base, and it isn’t in a third party library you’re using, you can’t do anything about this error.

Fortunately, Track.js lets you filter out error messages that you can do nothing about.

Read more about their filtering code and get the full story on their blog.

Did you like this?
CEO TrackJS
Todd is a software engineer, business leader, and developer advocate with 20+ years of experience. He is a co-founder and CEO of TrackJS and Request Metrics,...

What to do Next:

1. Try TrackJS on Your Website

TrackJS gives you the visibility to find and fix your errors before users find them. Get started in 5 minutes tracking errors with all the context you'll need to squash the important bugs in your app.

2. Get the Debugger Newsletter

Join The Debugger for amazing JavaScript tips, debugging walkthroughs, news, and product releases for Request Metrics. No more than once a week, probably a lot less.