Ranked in these QuestionsQuestion Ranking
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 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 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 Realtime notifications
See when new errors are happening in Slack or Hipchat rooms.
Pro Analytics dashboard
A snapshot of how you are doing, comparing page view volume to error volume.
Pro Wraps console.log for errors
All messages sent into console are included with error messages for additional context and logging
Con No deployments using a REST API call
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.