Bugsnag vs TrackJS JavaScript Error Logging

Clear, concise documentation. Plus docs on cross-domain script errors and enabling CORS.

Bugsnag can be set up to send email notifications as soon as exceptions occur. It can also integrate with a number of third-party services that can be used for notifications including Campfire, HipChat, Twilio SMS and custom solutions via Webhook.

Bugsnag integrates with a wide variety of 3rd party tools to automatically create issues or tickets. Integrations include GitHub, BitBucket, UserVoice, Trello and many, many others.

After a two-week full-featured free trial period the user is limited to 2,000 errors/month, 1 user and 1 project.

Bugsnag groups similar exceptions together displaying the number of occurences so that there's no need to deal with each instance of the error separately.

Their documentation was well organized, easy to search through for the platform of choice and quick work of full product integration.

Drop in place integration with Unity 3D, only a simple API Token configuration on game object and everything was up & running with almost zero code written.

Not many products have decided to finally start doing this, phabricator now has a champion.

Understanding the console, network, and user events that led up to an error makes it possible to recreate it in development.

Reports show what are the important errors to focus on fixing.

All messages sent into console are included with error messages for additional context and logging.

See when new errors are happening in Slack or Hipchat rooms.

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.

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.

You will always get an engineer who can understand and answer your question right away whenever you need help.

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.

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.

To ignore spurious errors.

TrackJs is very useful to catch console errors.

A snapshot of how you are doing, comparing page view volume to error volume.

No surprise bills caused by changes in usage.

Some general information like browser, operating system and viewport used by the client may help to determine source of trouble more precisely.