Need advice about which tool to choose?Ask the StackShare community!
Raygun vs Sentry: What are the differences?
Raygun: Use Raygun to track, manage, and report your software errors. Raygun gives you a window into how users are really experiencing your software applications. Detect, diagnose and resolve issues that are affecting end users with greater speed and accuracy; Sentry: 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.
Raygun and Sentry belong to "Exception Monitoring" category of the tech stack.
Some of the features offered by Raygun are:
- Error, crash and performance monitoring, in one platform
- Support for every major programming language and platform
- Minutes to set up
On the other hand, Sentry provides the following key features:
- 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.
- Integrate Everywhere: Drop-in integration for every major platform, framework, and language -- JavaScript, Python, PHP, Ruby, Node, Java, .NET, mobile.
"Easy setup and brilliant features" is the primary reason why developers consider Raygun over the competitors, whereas "Consolidates similar errors and makes resolution easy" was stated as the key factor in picking Sentry.
Sentry is an open source tool with 21.2K GitHub stars and 2.42K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
According to the StackShare community, Sentry has a broader approval, being mentioned in 1323 company stacks & 421 developers stacks; compared to Raygun, which is listed in 44 company stacks and 6 developer stacks.
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...