Sentry Recensies & Productdetails

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 quick install with just some lines of code. Much easy to get notifications across email, messages, or chat as part of a present workflow when mistakes occur or resurface. I like that error tracking system which is built for community.

Nothing to say bad about that software. As for me and my working team, we like every step of the working process. We never had problems with the tracking system.

We can make better sorting, reproduce and solved errors with maximum performance and appearance. We have the ability to exception handling with this platform helps developers make better apps and repeat quicker.

Very fast and detailed error reporting!!

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

Faster and easier debugging!

We've been using Sentry as an error reporting tool. The performance is great where one can expect timely alerts for all the events triggered across servers. The traceback can be easily understood and one can get to the problem very easily.

There can be better filters for notifications, otherwise one can get bombarded with emails.

We wanted to catch bugs early on and sentry does a great job. It reports front-end JS errors and my backend php errors with complete stacktrace which makes it very easy to fix them.

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.

Sentry has error handling clients written for almost every technology that our company uses. In addition to the Python and JavaScript client libraries, they have additional libraries that plug right into common development frameworks like Tornado, Django, Angular, etc. Installation of these client libraries is amazingly simple.

There is a lack of embeddable widgets on error metrics. We'd like to make it easy for us to create/share/export a generic dashboard and/or graph to view all stats (not just Sentry). That being said, they do have an API that allows the end user to fetch the error events (so that you can plot them on your own).

This helps us maintain uptime (especially on new deploys). Keeping track of new, occurring, and regressing errors helps our engineering team prioritize what to work on.

Sentry is extremely fast at gathering all the information necessary to debug an exception. It also groups them into accurate categories and provides permalinks to each error for reference. I always make sure that, when I start a new project, I get the Sentry project access key and integrate Sentry right away. Without it, I feel blind when I am debugging errors on our servers.

The search feature could be better. You can't always construct the exact search that you want, narrowing down to a specific error message at a specific time on a specific host accessed via a specific path. You can usually get there by browsing and filtering, so it's a minor nitpick.

I am a developer on a medium-to-large team and use Sentry for debugging errors in our API that serves our mobile apps. The main benefit of having Sentry is an indexed and searchable error log to quickly find and reference recurring exceptions.

- Multi-language support: allows us to track our Python and Javascript errors with a single product - Ease of settings in the web interface: limits domains, notifications frequency - Possibility to track all events: messages, exceptions, etc. - Two offers: SaaS (not free but all is managed for you) or instable on your own server for free - Integration with Trello, to pass information through our different SaaS

- No way to filter/categorize elements in the interface to filter events after in the main list (except by assignation to people...). It is possible to set tags only when the event is fired... - Javascript errors catched are sometimes not our concerns (e.g. Skype plugin or third party bug) - No sandbox to test configuration before deploying in production

Mostly bugs in production and have a better communication about it: we notify people who have encounter problems once bugs are solved. Customers says we are pretty reactive on this point and Sentry is a big help in this. Also help us to reproduce bugs thanks to context user data like browser or inputs done.