Sentry vs Backtrace: What are the differences?
Developers describe Sentry as "Cut time to resolution for app errors from five hours to five minutes". Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time. 500K developers use Sentry to get the code-level context they need to resolve issues at every stage of the app lifecycle. On the other hand, Backtrace is detailed as "Real-time automated error detection, response and analysis for enterprise-grade software". It is the first debugging platform built for enterprise-grade software. It improves system availability, software quality and team efficiency by bringing automation to incident detection, response and resolution. The debugging platform automatically snapshots faulting applications and their surrounding environments then, analyzes and archives them in a centralized object store so bugs don't get missed and get fixed faster.
Sentry and Backtrace belong to "Exception Monitoring" category of the tech stack.
Some of the features offered by Sentry are:
- Real-Time Updates: For the first time, developers can fix code-level issues anywhere in the stack well before users even encounter an error.
- Complete Context: Spend more time where it matters, rather than investing in low-impact issues.
On the other hand, Backtrace provides the following key features:
- Automated capture, notification, and analysis of software errors for SREs/Ops and Developers
- Automated analysis crawls application state + code to give you a head start on root cause analysis
- Captures a rich data set which includes stacktrace across all threads, reachable variables, system information and much more
Sentry is an open source tool with 21.9K GitHub stars and 2.53K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
I essentially inherited a Shopify theme that was originally created by an agency. After discovering a number of errors being thrown in the Dev Console just by scrolling through the website, I needed more visibility over any errors happening in the field. Having used both Sentry and TrackJS, I always got lost in the TrackJS interface, so I felt more comfortable introducing Sentry. The Sentry free tier is also very generous, although it turns out the theme threw over 15k errors in less than a week.
I highly recommend setting up error tracking from day one. Theoretically, you should never need to upgrade from the free tier if you're keeping on top of the errors...