Blog Home » Filtering JavaScript Error Reports at Cornell

Filtering JavaScript Error Reports at Cornell

By Todd H Gardner

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.

Todd H Gardner
Todd H Gardner
CEO and Cofounder