www.capterra.com
Sentry Reviews 2026. Verified Reviews, Pros & Cons - Capterra
Excerpt
Cons Setting it up with your backend server for the first time can take some time. Also we faced some issues with integrating the HTTPS sentry link with Node.js. Other than that, its a great tool in helping you keeping your production environment available 24/7. Review Source VL ... Cons 1\. Need a bit of knowledge of error reporting to work 2. Some kind of tutorial video or detailed blogs are needed to use. 3. The team plan is very pricy 26$ per month. 4. No benefit for student or startups. Switched from [Firebase](https://www.capterra.com/p/160941/Firebase/) … 5.0 ... Easy to set up Lots of details about each error Ability to quickly ignore, postpone, assign errors Cons A little bit hard to search through the resolved issues Emails about new errors sometimes go to spam, with multiple emails providers … December 15, 2017 4.0 Pros ... Cons API clients don't support asynchronous communication, you need to implement it by yourself. Besides, it is possible define fingerprints to track issues, but it is not possible to filter the issues by fingerprints. … Cons It would be handy if there were more statistics available about error rate maybe via their API. Also sometimes its hard to set up functionality like release tracking and sourcemaps etc. Review Source SE Sven E. Freelance Web Developer Information Services Used the software for: 1-2 years ... I love how it keeps track of errors, displays them and allows very easy tracking of error frequency and communicating about them. Cons Sentry doesn’t handle extreme quantities of errors very well. As a result, if there are a ton of errors at a time it might not even report a percentage of them. … Pros Relatively easy to use and tons of amazing features. I also like the UI a lot. ... Cons I had some issues setting up automated builds for the deploys of releases and maps. Due to the sentry cli not being easy to find and setup from documentation. Also, I had to figure out how to do it myself. It would be awesome if there was documentation on how to do it with a webpack build and deploy with sentry as well. … Cons I didn't receive emails for some of the bugs but that may have been my mistake. The dashboard is not very intuitive Review Source OI Omer I. Software Engineer Information Technology and Services Used the software for: 2+ years ### "Error Tracking and Reporting with ease" April 5, 2022 … Cons 1- Grouping of issue events is a bit strange sometimes if you don't write your own error handlers. 2- Documentation can be outdated sometimes. Reason for choosing Sentry Our first project was built with React Native Expo, which supported Sentry out of the box, so we decided to go with it.
Related Pain Points
Complex source map configuration breaks stack traces in production
8Source maps are difficult to configure and frequently fail, leaving developers with minified/unreadable stack traces in production. Teams spend days debugging source map setup instead of actual bugs. This is a critical blocker for production debugging.
Missing stack traces from error loops and cascading errors
6When errors occur in loops or trigger cascades, Sentry may not report all events or provide useful debugging information. The 5,000 event monthly limit can be exhausted quickly by repeating errors, leaving no visibility for other issues.
Poor observability in email delivery
6Most email service providers offer limited visibility into what happens after an email is sent, making it difficult to debug delivery failures and understand the full lifecycle of sent messages.
Documentation outdated and incomplete for some platforms
4Documentation can be outdated and is incomplete for less common platforms. WordPress documentation reported as nonexistent. Users frequently rely on community solutions or trial-and-error. Some integration documentation is behind schedule.
Error grouping produces strange results without custom error handlers
4Automatic grouping of similar errors behaves strangely if custom error handlers are not properly implemented. Teams need to understand and configure error fingerprinting for reliable issue grouping.
Complex setup for backend integration, particularly Node.js HTTPS
4Initial backend setup can take significant time. Integration issues reported with HTTPS Sentry links in Node.js. Backend integration is more complex than frontend setup and requires domain knowledge of error reporting.
Limited statistics available via API for error rate analysis
3API provides limited statistics for error rate analysis. More granular error rate metrics would be helpful. Limited programmatic access to metrics compared to competitor offerings.
Difficult to search through resolved/archived issues
3User interface for searching and filtering through resolved issues is not intuitive or efficient. Time-consuming to find historical issues or archived data.
API clients don't natively support asynchronous communication
3Sentry API clients lack native asynchronous communication support. Custom implementation required. Additionally, filtering by fingerprints is not possible despite fingerprint tracking being available.