When comparing Airbrake vs TrackJS JavaScript Error Logging, the Slant community recommends TrackJS JavaScript Error Logging for most people. In the question“What are the best JavaScript client-side error logging services?” TrackJS JavaScript Error Logging is ranked 1st while Airbrake is ranked 7th. The most important reason people chose TrackJS JavaScript Error Logging is:
Understanding the console, network, and user events that led up to an error makes it possible to recreate it in development.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to use UI
Airbrake.io boasts a beautiful user interface which gives easy access to features such as intelligent error grouping and application insights, session details and backtraces. All these allow you to squash those bugs at a much faster pace.
Pro Airbrake errors can be self-hosted on Errbit
Errbit is a self-hosted error catcher for Airbrake. It allows keeping errors off Airbrake's servers by using Airbrake's error tracking tools to send error logs to your own ErrBit based web service. Useful for when errors contain sensitive client data.
Pro Asynchronous error tracking script
By including Airbrake's client side error tracking JS into your code, you won't have to worry about it affecting your page load times at all. Since the library loads asynchronously, which means it won't cause painful delays for your site's visitors.
Pro Easy integration with other applications
Airbrake integrates easily with Github, Hipchat, Asana and a number of other services, which can be viewed here. Also if you've got a custom app you'd like to integrate into Airbrake, you can use Airbrake's public API or there web hooks functionality to your advantage.
Pro Telemetry timeline
Understanding the console, network, and user events that led up to an error makes it possible to recreate it in development.
Pro Error trends
Reports show what are the important errors to focus on fixing.
Pro Wraps console.log for errors
All messages sent into console are included with error messages for additional context and logging.
Pro Realtime notifications
See when new errors are happening in Slack or Hipchat rooms.
Pro Ability to track an error down to a specific customer (if necessary)
TrackJS supports custom user IDs, which can be random strings that we, the customer can assign to a certain user. This helps a lot when handling a support request or a bug report from customers.
Pro Daily summary email
You can see how your site is doing every day with a summary of all the interesting activity and errors that should be checked into.
Pro Engineer Support
You will always get an engineer who can understand and answer your question right away whenever you need help.
Pro Highly customizable with custom JS code on the page
Hooks in the code that let you customize just about anything, you can get the error object before it's sent to the server and do whatever you like with it.
Pro Inline sourcecode snippets
Error messages and stacktraces are shown with snippets of the raw source at the location. This gives a ton of context to quickly find the error.
Pro Powerful ignore rules and grouping rules
To ignore spurious errors.
Pro Find bug in product easily
TrackJs is very useful to catch console errors.
Pro Analytics dashboard
A snapshot of how you are doing, comparing page view volume to error volume.
Pro Very useful product for use and tracking issues
Pro Personal touch customer support
Pro Predictable Billing
No surprise bills caused by changes in usage.
Pro Client specs
Some general information like browser, operating system and viewport used by the client may help to determine source of trouble more precisely.
Cons
Con Non-free / propritary software
Airbrake is non-free software, so it cannot be self-hosted, audited, or improved upon by the community. Your data is insecure - open to be read by Airbrake Inc, and if they shut down you will be unable to continue using the software.
Con No integrations on the free plan
Con Multiple errors from the same user can bloat your metrics
No "distinct" error count. If a loop ends up inflating a single user's error count, all reports are affected. Dashboard skewed by weird outliers.
Recently (as of February 2018) sorting by "users impacted" was introduced to reduce this problem.