JavaScript Error Tracking

There are no images or videos added to the gallery.
Add to gallery



You need to become a Contributor to join the discussion - Find out how.
Dave Mulder@muldster · Head of Product for @conferencesio
Hello @toddhgardner! How does {Track:js} compare to other JS error monitoring products like BugSnag and New Relic? Is your product for everyone, or is it for customers with some specific needs?
Todd H GardnerMaker@toddhgardner · Founder, TrackJS
@muldster Good Question, we operate in a similar space. BugSnag, NewRelic, and others are good tools and they solve a lot of problems. They have their origins in server-side error tracking, where the exception is the near-complete expression of the problem. If you have the stack, you probably have everything you need to debug. The client-side is trickier. JavaScript errors are terse and uninformative. Worse, browsers differ in their implementation of Error, so the information received varies wildly. TrackJS is unique in that we include analytics about what the user, the network, and your application are doing leading up to the error. Our Telemetry Timeline gives the developers the steps to recreate and resolve errors. We also wrap and normalize the error, making it far more likely to capture detailed error information than the other players. In short: we're focused. We solve JavaScript Error Tracking for modern web applications.
Jason CrawfordPro@jasoncrawford · Chopping wood, carrying water
We've been using TrackJS for about a month and it's been pretty good. The stack traces and event logs are very helpful.
Todd H GardnerMaker@toddhgardner · Founder, TrackJS
Thanks for everyone's support! Webapps are hard; we're trying to make the web a little bit better :)
Oleg Campbell@olegcl · CEO and Founder @ Reply
Amazing product!