BugSnag vs. Sentry

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
BugSnag
Score 8.0 out of 10
N/A
Bugsnag is an application health and error tracking application, now from Smartbear since the April 2021 acquisition, for monitoring web application stability, and alerting developers to app issues and error-rate in real-time.N/A
Sentry
Score 9.1 out of 10
N/A
Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
$26
per month
Pricing
BugSnagSentry
Editions & Modules
No answers on this topic
Team
$26
per month
Business
$80
per month
Developer
Free
Enterprise
Contact sales team
Offerings
Pricing Offerings
BugSnagSentry
Free Trial
YesYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
BugSnagSentry
Best Alternatives
BugSnagSentry
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
BugSnagSentry
Likelihood to Recommend
10.0
(0 ratings)
8.3
(0 ratings)
User Testimonials
BugSnagSentry
Likelihood to Recommend
It's great for tracking bugs on your app. I don't think I can do anything else besides that...
Read full review
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
Read full review
Pros
  • The UI/UX is well designed. I have never been confused by any buttons/filters/settings, and everything is laid out in a neat and organized fashion.
  • Setup was super easy. I didn't have to do anything but read the documentation, which was well written.
  • The information captured by errors has everything I would need to debug an issue.
Read full review
  • It collects very detailed information on problems that happen to our users while using the platform
  • It supplies very good tools in order to aggregate the collected data and analyze it
  • It integrates with Slack, making it easier to "monitor it in real time"
Read full review
Cons
  • For really long bugs, it'd be nice if you hovered over the row and it expanded the text so you didn't have to click on the actual bug to view everything.
  • It would be nice if there was a filter for grouping bugs instead of searching by their name.
  • Honestly nothing else, I love 99% of Bugsnag.
Read full review
  • if we could decrease the costing via some kind of sampling of errors.
  • sometimes same error is in loop and Sentry will count all the events for pricing if there is any way this can be reduced.
  • self hosted capabilities or using own storage to reduce cost.
Read full review
Alternatives Considered
No answers on this topic
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.
Read full review
Return on Investment
  • It has caught bugs on the spot, which allows us to quickly fix them.
Read full review
  • Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
  • Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...
Read full review
ScreenShots