TrustRadius Insights for Sentry are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Many users have praised the clean and user-friendly interface of Sentry, describing it as great with a clean format. They appreciate the intuitive design and easy navigation, which contributes to a seamless user experience. Reviewers have also highlighted the exceptional error tracking capabilities of Sentry. The per-user exception tracking feature allows users to easily identify and investigate issues by looking up account IDs and reviewing encountered exceptions. This comprehensive approach enables effective debugging and troubleshooting. Several users have commended Sentry for its generous free tier, offering 10,000 events per month. They express satisfaction with the ample availability of event tracking provided by this free plan, indicating that it meets their needs without any additional charges or limitations. Overall, these three pros are consistently mentioned by reviewers and contribute to the positive sentiment expressed about Sentry.
We use sentry primarily for application monitoring, our biggest use case of sentry is log and error monitoring. For our money Sentry is best at it, it gives full views of errors that happen on your applications with incredible captured details like causes, lines and other specifications we couldnt find in other platforms we were considering.
Pros
Error capture
Application monitoring
Session replay
Cons
Custom queries can be a little complicated to work with
Pricing can get a little steep
Likelihood to Recommend
If you are just getting started and looking to scale Sentry is perfect, for us we were using it on NodeJS and we simply had to install a few lines of code to making it work in minutes.
Alternatives
Rollbar, Dynatrace, Splunk Application Performance Monitoring (APM), Datadog and Grafana
VU
Verified User
Team Lead in Engineering (Computer Software company, 1-10 employees)
We have many microservices and its very important to monitor them for errors and any other bugs. So we needed some dashboard where we can see the full trace of the error occurred while the user was using our product and Sentry just does that. Its so easy to integrate and see the error traces with the information of user and the line from where the error originated.
Pros
Get the full trace of the error.
Integrations like slack for errors if you can't see dashboard everytime.
Different kinds of alerts like slack, email and grouping of alerts.
Cons
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.
Likelihood to Recommend
Some of cases would be:-
get full trace of the error occurred with user information like primary key.
Grouping of similar kinds of errors.
Assigning the errors to someone from company and creating it as a jira issue for resolution tracing.
differentiating errors according to the environment where they occured.
role based access for the dashboard for different users of company.
Alternatives
Rollbar
We used rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people in company where not able to understand rollbar dashboard who were very much used to Sentry.
We use sentry for monitoring and tracking errors in our system. We have set up our own self-hosted instance for monitoring multiple systems. In fact multiple instances of sentry for different orgs. We heavily used it for alerting and identifying unknown or uncaught exceptions and also real time alerting for the same.
Pros
Integration with application is quite simple
Tracing exception and storing relevant info for simpler debugging
User interface is quite simple and easy
Integration with Slack or similar platforms for alerting
Cons
Simpler and much configurable alerts, sometimes it doesn't look too intuitive
It is very resource heavy and not that cost friendly
Data sampling could be better
Likelihood to Recommend
It is well suited for a company that is somewhat okay with spending money on extra monitoring. But it is not for a company that is very small in size, because it is not really required for such small-sized applications and also brings the cost of operation higher. But it is a very useful tool if you have decent traffic in your systems and require aggressive monitoring
Alternatives
AppDynamics and IBM Instana
Both AppD and Instana are a superset of sentry the majority of the time. Sentry is specialised in error tracking does the best in it, but the other too mentioned does a similar job along with multiple other monitoring features. Also, sampling of data is best in Instana, and is not that great in Sentry.
VU
Verified User
Engineer in Engineering (Health, Wellness and Fitness company, 201-500 employees)
Sentry is being used across all the cloud teams at our organization. It is helping us to monitor all of our production applications and get real time alerts when any issues arise. It integrates into Slack as well which helps us facilitate issue triage and incident management.
Pros
Great user experience
Real time alerting
Wide range of supported SDK languages
Cons
Alert Configuration. Would be really helpful to have multiple logical groupings within the "If" section of a single configurable alert.
Alert Copying. Being able to copy an alert from one project to another would be super beneficial.
Alert Tags. Better UI around how we select which tags are getting sent with each alert instead of a tiny text box.
Likelihood to Recommend
[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.
VU
Verified User
Team Lead in Engineering (Information Technology & Services company, 201-500 employees)
Sentry is being used by the engineering department and it addresses our issue with tracking exceptions that occur with our software. This gives us a proactive indication of a possible issue in production or other environments. By being proactive about detecting exceptions we have a chance to fix them before customers even notice.
Pros
Great at giving us a proactive heads up when there may be a serious issue in production by notifying us when a certain exception happens many times.
Excellent variety of supported platforms: .NET, Java, and many more.
Tracks exceptions across multiple releases, so you can identify when an exception first started happening.
Cons
Sentry rolls up exceptions that it feels are similar, but the logic to determine that similarity could be improved. It doesn't always merge exceptions that are similar.
The UI could be improved around projects; it would be nice to be able to group them by an environment.
Support for .NET could be improved, it required us to roll our own library to log to Sentry.
Likelihood to Recommend
Sentry is well suited for SaaS projects that wish to track exceptions happening in the backend. While it can be used for desktop applications, it may not be as suited for such projects. It works well to get real-time exceptions and aggregate common issues. If you don't have a team or staff to deal with the notifications then it may not be of as much use.
Alternatives
New Relic
Sentry is better suited for tracking and aggregating exceptions over New Relic. New Relic does report on exceptions that occur, but Sentry is better at rolling up similar exceptions and filtering out the noise. Sentry also does a great job at identifying when an exception first started occurring and sorting by recent/most frequent exceptions.
We use Sentry for monitoring all production web systems. Sentry solves a really important problem for us: in production, we'd like our services to automatically recover if (when) they go down, have errors, or throw exceptions. That's a problem from an error reporting perspective because we then lose failure state on reboot. Sentry helps us bridge this by logging and reporting production errors, so we can actively work to fix them, but don't have to worry about systems staying down while we work to triage.
Pros
Sentry doesn't just provide a list of errors and exceptions, but instead gives us a full stack trace to work from
Internally, Sentry handles a lot of code versioning checks so we can see where errors originated from, and if deployed fixes are in fact working
Sentry interfaces with existing reporting tools so we can respond to production exceptions in minutes, instead of when we find out about them in viewing logs
Cons
Very much a one-off tool; Sentry would be a lot nicer to use if it built out additional monitoring tools so we could run the entirely of our logging and reporting through their software
Some of their documentation, particularly for the open source projects that drive error collection, can be lacking or inadequately communicated
Likelihood to Recommend
Sentry is well-suited for any organizations with important production systems. The nice thing about it is it's an agnostic tool that can be used regardless of what kind of project you're working on -- you can just drop it in and start using it. The only real issue with it is that for clients with particular PaaS and LaaS restrictions, it may not be possible to allow code stack traces to be uploaded to third-party services.
Alternatives
OverOps, Airbrake, Raygun, PagerDuty and Pingdom
Sentry is really a tool to be used in combination with other things, like Pingdom and PagerDuty. For those applications, Sentry is a far more full-features offering that lets you see why errors happened, not just be alerted to their occurrence. We chose it over other error monitoring applications based on flexibility and ease of use.
We are using Sentry to help us capture, track, and mitigate issues with our website users. We have the client Javascript SDK (called Raven) loaded on each page load, and we're using the raven npm module on the server. Most of the exceptions get caught automatically, but we also use the manual error-tracking features in a few places where we want to track unwanted outcomes without throwing exceptions.
Pros
Great web interface. Lots of data available in a really clean format, with filtering options and more.
Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
Very generous free tier – 10,000 events per month. We're nowhere near that yet.
Cons
Rollbar has more integrations with other services such as Help Scout. Would be nice if Sentry had as many.
Can't search for users by username, even though I'm supplying one with the client SDK. I have to find their database ID first.
Likelihood to Recommend
Sentry supports a wide range of platforms and languages, so it seems well-suited to capture exceptions in many different kinds of apps and websites.
Alternatives
Rollbar
There are quite a few players in this space, but Rollbar and Sentry seem to be the top two. I can't remember why I chose Sentry over Rollbar, but they seem pretty close in terms of features.
