Sentry Reviews & Product Details

It's been fantastic in letting us know when a customer has experienced any issues in our checkout process or other areas of the website. Now instead of flying blind we can actually know within the second someone encounters an error and can begin fixing it.

The email notifications can be heavy if you don't do some tweaking and filtering. I was getting bombarded with every little js error the front end console would encounter. I wouldn't really count this as a negative against Sentry, since this means it's doing its job. But setting up filters in the front end script and being able to mute errors has made it more manageable.

Even though this might not be its primary function for most people, we can now see when someone hits a dead end in our checkout process. This has been fantastic in improving conversion rates now that we can spot the problems before anyone else has to encounter them. It's hard to imagine how many visitors might have been encountering process halting errors before now (and worse, how many could've bounced from it). But Sentry has been a huge help in rectifying those problems. I highly recommend it!

I really liked Sentry's interface and pricing, plus the Heroku integration made it super easy and simple to get set up. Sentry supports tons of languages, offers a lot of cool integrations, release tracking and more. I was really happy with it and it helped me, as sole-engineer/CTO, keep on top of bugs and issues with our app. I would definitely use Sentry again.

Honestly I didn't really have any complaints with Sentry when I used it. The interface was a little clunky when I started using it, but that has improved a lot since then. They've also added more language support.

Sentry helps your team stay on top errors and issues within your app and helps you to diagnose the problem and find out where/when it was introduced into your codebase.

- full traceback - local variables - showing source code

Not supporting MySQL anymore. Outdated on promise version.

Easier error logs. Faster tracking of errors.

It helped me find out obscure cases in which my client code would fail, that otherwise would be harder to find out about.

There is some lee-way in terms of volume, but I feel that the reporting volume in the free version is a bit too low.

Various end-case Javascript errors,

I like its built int clustering and throttling, and smooth presentation of important information like stack trace.

I dislike how you cannot have different lists of people to notify, and key off of tags or other things to decide which list to send to. We're at the point where we have 25 engineers and emailing all of them for each error does not make sense.

We want to be notified when production errors are encountered, but not flood our inboxes.

It is my first choice as a crash reporting tool for web, mobile and games. It has support for the latest languages such as JavaScript, Ruby, Python, PHP, and Node.js. It shows me the exact performed actions from the users which has led to the crash and thus providing a deep insight for the actions as well as the related workflows which have caused the error and definitely it is of great use for me to debug the problem.

It will provide you with lots of features but when it comes to the trail of events it may fail helping you. It is surely not helpful for you to show a historical event of errors and bugs which have occurred. If you want to capture other issues with the code, you cannot expect much from the tool with that too.

I have been suing it and found that it is very easy to operate and can be started of easily with the documentation. It will notify the affected users about the crash so that they are aware that they have encountered an error and it will be resolved pretty soon. It automatically prompts the users for feedback so that they know when things aren’t working fine. You can also get to know about the details like where error has happened, its frequency and the affected users. You are free to choose from the notifications options from a range of email, SMS, or live chat when any error occurs.

You can track error for multiple languages on a single app, for example, if you use Laravel you can check for PHP errors and Javascript at the same time. This is very useful, because usually you require users to report the error, this way you discover any errors on-the-fly and you can respond accordingly. Also has trello support which is a plus for me.

It's a pay software and the price is too high (At least for me), It would be nice if they put up a free-tier or a 1-2 person tier for half a price.

Sentry hepls you monitor errors, exceptions and warnings for Small to Large proyects without the need for user reporting.

The UI is good. The reports are good and usable.

It gets down so many times, and troubleshooting is aweful.

We use sentry for error handling and logging. You can have multiple projects and teams and separate them easily. It can be connected to Jira and GitLab, so you can make issues and tasks directly from an exception that is logged in sentry.

I've been using Sentry for years and a tool like theirs is needed to track and monitor/share bugs across dev teams.

Sentry makes it very difficult to contact support. Additionally, they have numerous bugs and limitations baked into the platform. I even reached out to them on Twitter and was promptly ignored. This is one of those companies where you can't wait for a competitor to come along and steal the show because they don't deserve the customer flow they get. They get customers because they are the standard in the space, not because they're any good.

Support is very difficult to find. They don't answer social media. They limit your plan in every way possible until you go to the next tier up. Even when you do upgrade, the limitations still exist and you have to contact customers support which is very difficult to do. They've recently hid all of my bug reports (i'm sure it was accidental) but it's seriously disrupted our work flow.

The fact that it shows regressions is very useful. A bug can appear and be fixed, and if something down the line causes the same error, it doesn't show up as a separate problem-- so you can really keep tabs on things that you thought were fixed but maybe weren't.

I've found an unusual and very problematic bug with the account management-- I had a previous Sentry account with another company, and after changing jobs, I've found that no matter what I do, I cannot log in to the new company's single sign on page in Sentry, rendering it pretty much useless. This is a niche problem and one that doesn't seem widespread, but significant enough that it's hard to really recommend this to another user with full enthusiasm.

It keeps track of bugs and lets you see the stack trace of said bugs, so it's very effective at keeping tabs on problematic endpoints and you can circumvent a client's frustration if you can see what they are experiencing from a backend perspective.

There are many softwares available for web analytics but I've found sentry to be the best. Very easy to setup and dashboard is also very easy to use. Many other softwares are lacking the features that sentry provides.

The dashboard looks a little cluttered. It can be improved. I really like the UX of Firebase Crashlytics, so something similar can be done here as well.

Sentry helps finding the bug on the website. It tells you exactly where things went wrong with the help of mentioning the line number of the source code.

I like the versatility of Sentry, which provides different dimensions of application observability, including metrics, tracing, and error tracking.

The UI is a little too complicated and disorganized for a first-time user.

Sentry helps boost software development experience and efficiency with its versatile observability coverage and rich support for different programming languages.

We can send and analyse the application issues using the comprehensive details in sentry.

I think, the configuration options should be increased.

Helping to catch & analyse the issues and errors in live applications

Ease of implementation, user interface, and the ability to detect and handle bugs proactively.

Not all features are available for the Flutter SDK

Detecting and handling bugs before the final users complain about them.

I love the email notifications but only for new errors.

There is sometimes a delay with the error reporting.

It makes looking at the stacktrace in production errors so much easier

A great error reporting and tracking software that is open source and allows you to build custom solutions for your needs

sometimes finding answers to questions can be hard to find in the docs.

We use sentry to track exceptions that we catch in our applications, we are also able to see graphs of errors and users affected.

Sentry helped us figure out many production issues with very little effort. All events are aggregated into easy to parse messages.

The searching capabilities do not seem very thorough. I have tried to search by url and still come up short :/

Metrics, bug tracking and visibility into out production instance.

Most of it is open source, it's easy to get started, documentation is good, works pretty much anywhere/everywhere, it's reliable, I've had no issues so far (~1 year of use).

The settings/configuration feels complicated when working with many projects (shared vs. project-specific settings). The previous version used to have a nice feed/view with the most recent exceptions across all projects; now I have to open each project to see if there's anything new.

Stack tracing and error reporting - especially on the client side (javascript in the browser).

Very fast and detailed error reporting!!

Nothing.Nothing.Nothing.Nothing.Nothing.Nothing.Nothing.Nothing.

Faster and easier debugging!

I like it's trace of the code. It is the best way to debug the whole trace. Most importantly, checking the request and finding the exact cause of error helps to quickly solve the problem.

The Interface. Although the Web Interface is quite good but I believe it can be improved. Improving to include the variables values at the time of error. Moreover since it already groups same types of errors, it should be grouped with same type of requests also.

I am in a team that manages intranet system of our institute. We get 500 errors daily and every evening sentry helps me to debug all the problems efficiently.