TrackJS gives you context about what's happening in your end-users' browsers. The Telemetry timeline recreates all the application, network, and user activity that leads to an error. The stack trace processing shows you the code you need to investigate.
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?
@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.
At Shutterstock I've been building an all front end design and photo editing tool for the last three years called Shutterstock Editor. Without trackjs we would be blind too all the problems that can happen in an app that depends on webgl, undo history, complex user interaction, and many other user interactions over the hours our users work on marketing design material.
No other app bubbles up real errors by user impact in as a clear a way as trackjs. I don't see how you could build a front end app without it.
Request Metrics
Versus
AudioAlerts.io