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.
What is LogRocket?
What is Sentry?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using LogRocket?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Lots of companies I respect were using it + open-source + great features and UI. Went for the hosted version, since it plays nice with Heroku. I like how they group together similar errors, give you the ability to mute events or mark them as solved. P.S. check out the Founder Stories feature we did on Sentry if you want to know how they started, its an awesome story.
The error and event tracking in Sentry is superb. Being able to assign the raw error to people along with all information at the time the event occurred means that we're tracking and fixing problems before they become apparent to customers. We use the self-hosted instance of Sentry.
Sentry is a very powerful error reporting tool. We use it both on front-end and back-end of Ataccama One. It proved to be invaluable in providing insights on our errors - what caused it, what user did before the error occured, stack trace, release tracking and more.
We use Sentry to gather our thrown non-checked exceptions in one place, so we don't have to crawl through all our logs manually. All standalone-applications, our website aswell as our game-servers are linked into sentry.