LogRocket vs Sentry: What are the differences?
Developers describe LogRocket as "Record everything users do on your site, so you can reproduce bugs and fix issues faster". LogRocket helps product teams build better experiences for their users. By recording videos of user sessions along with logs and network data, LogRocket surfaces UX problems and reveals the root cause of every bug. On the other hand, Sentry is detailed 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.
LogRocket can be classified as a tool in the "User Feedback as a Service" category, while Sentry is grouped under "Exception Monitoring".
"See a video of user using your website" is the primary reason why developers consider LogRocket 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.4K GitHub stars and 2.45K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
Airbnb, Uber Technologies, and Instagram are some of the popular companies that use Sentry, whereas LogRocket is used by Teleport, Drawbotics, and SupplyAI. Sentry has a broader approval, being mentioned in 1341 company stacks & 436 developers stacks; compared to LogRocket, which is listed in 68 company stacks and 11 developer stacks.
In our organisation we are currently signed up with Logrocket which sessions out at 30001 Milliseconds that's basically 15 days usage in a month rest of the month we have to either live without it or pay more. Now I want to know the following Where (Software) are the best use for LogRocket Which are the applications that would be primary How is Sentry different from LogRocket How can I optimize my sessions.
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...