Exceptiontrap vs Sentry: What are the differences?
Exceptiontrap: Error tracking & monitoring for Rails and PHP. Exceptiontrap is the simple and powerful error tracking and exception monitoring service for Ruby on Rails and PHP; 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.
Exceptiontrap and Sentry can be categorized as "Exception Monitoring" tools.
Some of the features offered by Exceptiontrap are:
- With Exceptiontrap you know that your app runs smoothly in production.
- Exceptiontrap makes it easy to handle your app errors in a team. At the dashboard everyone sees whats going on and if there is something to do.
- The Information You Need: You can see all your apps information you need to know what was going wrong at one view. You can see all the information related to the error.
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.
Sentry is an open source tool with 21.4K GitHub stars and 2.44K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
What is Exceptiontrap?
What is Sentry?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Exceptiontrap?
What companies use Exceptiontrap?
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.