When comparing Sentry 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 Sentry is ranked 2nd. 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 Consolidates similar errors and makes resolution easy
It's what Sentry calls [Rollups](https://docs.sentry.io/learn/rollups/]. All individual issues rolled-up can still be drilled down. Also two issues can be merged manually.
Pro Email/Slack/GitHub/Hipchat integration
Newly discovered issues (i.e. one that isn't rolled-up under and existing one) can generate an instant notification via many means.
Pro Has an official Docker image
Sentry has an official Docker image which means it's likely going to be well reviewed and maintained for a while and it makes it easy to set up.
Pro Completely open source, with a hosted version available
Sentry is a completely open source tool. It's free to use if you want to run it on your own. If you want to avoid the overhead of running and maintaining another server, it also has a hosted version available at www.getsentry.com
Pro Source maps support
Has support for source maps.
Pro Can create projects and teams
A single Sentry server can be used for various teams/products.
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 Not really a logging solution
Sentry collects exceptions, it's not a solution for log aggregation.
Con Can't filter by browser versions
Sentry only filters by browser names and not by browser versions (for example: Firefox, instead of Firefox 27, Firefox 28 etc...)
Con No free cloud hosting
Unfortunately there is no free plan for cloud hosted solution. Only self-hosted solutions are free to use.
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.