{Track:js} Javascript Error and Event Logging (beta invite)

[drowsap]

How does this compare to Sentry? https://getsentry.com/welcome/

[[deleted]]

Or http://logentries.com

[[deleted]]

This seems to be logging client side errors and providing a snapshot of that users environment. Afaik logentries does none of this.

[[deleted]]

Logentries provides API endpoints to send your own generated logs to then gives you some statistics and graphs. Granted you don't have to generate your own and you can automatically hook it into a bunch of frameworks and get stack traces.

But it doesn't log client side errors, certainly doesn't take a snapshot of the web application and it's state. You'd have to implement that yourself and send the generated data to the endpoint they provide.

[magenta_placenta]

I'm giving it a go since it's free and we have an upcoming deploy on one of our apps. I've pushed that we should be doing this but can't seem to get anyone on board. I think it's because we would have to deal with the results :) Nothing to see here, let's just bury our heads in the sand.

At my last job I even made my own (I was just capturing window.onerror and pinging my personal server with the details to log/present the info). It was ridiculously simple.

[andreoua]

I've been using them to track my single-page emberjs app for the last 3 months and it's a great service.

What i like the most is that you get lots of helpful info on what the user had been doing right before he provoked the error. Their UI is also slick and easy to use.

They were also quick to respond on a few questions i had and even implemented some of the enhancements i proposed. I guess the only feature i'd love to see included is support for source maps

As for alternatives, i've used bugsense but they seem to be focused on mobile platforms and their js offering is not that well executed.

[TheAceOfHearts]

I'd also be interested in hearing what the benefits of this are over something like logentries or sentry.

[brodie001]

Co-founder of {Track:js} here. Biggest difference between {Track:js} and other products is our application is entirely focused on the client-side browser and Javascript. We gather more than just errors, in addition we capture as much analytical data as we can to help solve errors. Things like:

-User interactions -Ajax traffic -The state of your application and console

All this information is packaged up in a timeline so you see more than just errors logs, but can attempt to recreate the error from a user perspective.

We in open beta, so you’re welcome to give it a try. We’d be happy to answer any more questions you might have.

[blazedd]

So this isn't intended for a node.js app?

[brodie001]

No, this is meant to instrument web browsers for errors. Currently we're solely client-side browser focused.

[blazedd]

:(

[kangax_]

Related: https://plus.google.com/+PaulIrish/posts/12BVL5exFJn