Sentry Comentários e detalhes do produto

As for me, I can just use few lines of code to set up this system and it takes only a few minutes. I'm glad that system works fast and I can save my productive time. Also I have the ability to have notifications via my email or push messages as part of an existing workflow when mistakes happen.

At beginning of my journey with Sentry I really need help from somebody who knows how to start to work with this. Support service always helps to solve a problem or help with any info which I need.

We are working on how to fast find and reproduce bugs and resolve issues with max effectiveness. We are glad to work with Sentry, as it helps to develop better apps.

For me, the most convenient is track errors for multiple languages on a single app. Pretty easy to install and set up.

I would like to have more effective filters to send out the messages, otherwise I received tons of emails. Also, I would like to see a better search function.

We use Sentry for our projects with AngularJS and Android, and it works wine. Bugs tracking with it help me and my team monitor and fix crashes in real time. We can tag and filter our data so that we get a full view of the problem and can fix a bug usually in an hour or even less.

Performance Sentry for tracking errors is very high. This helps very quickly to find and fix the problems that arise. Sentry fits perfectly with other tools. What else I like is the ability to create additional filters. This can be extremely useful.

I would not call the user interface very successful. Sometimes there may be problems with setting up notifications, otherwise you can get dozens of notifications about the same error.

We have been using Sentry for some time, to generate error reports in our projects. This service allows us to track errors and failures in time, as well as to explain the reason and eliminate it. This helps to significantly improve the efficiency of our work and its quality. Sentry - is indispensable for a new project, because it helps to solve the problem before someone collides with it.

Very like that now I have the great system of tracking common bugs. Actually easy to use and has a lot of amazing tools.Which will make your project be better.

Actually no real cons. I using that software at my company and I found out that its too great to have it. The perfect way to avoid a lot of mistakes.

Helps us to develop control and fix collapse in real time. Also making our work more efficiently.Great that we can develop user experience. Big helper, it that moment.

you can easily integrate sentry with Github to create issues, assign those to users, send messages to slack channels and have a good real-time control of your system's health.

the notifications settings can be tricky. It took some time until I was able to configure it properly to not be bombarded by emails.

I'm using Sentry to track/control bugs in five java ee systems. Sentry helps a lot given all required information and resources to reproduce and understand unexpected behaviors.

I can capture all the necessary information realtime yet don't overwhelmed notification queue because it does "intelligent" notification. Easy to configure and easy integration with Slack.

Project setup UI might not be the most intuitive UI

Issue to be instantly notify developers and proactively fix the issue instead of waiting for someone to report.

We have two hybrid applications written in Javascript with Ionic/Cordova. Without Sentry, it would be impossible to investigate a lot of problems/errors reported by our customers, we like the very detailed erros reports and the filtering feature that lets you search by operating system, device model, and so on. Also, Android Java exceptions tracking is very good.

I don't like frequent errors management: it would be nice, for the same error occoured hundreds or thousands of times, to filter single events by operating systems, device model, more or less like the general error filtering. It would be easier to isolate single events reported by specific customers.

It surely help to save a large amount of time while debugging, and makes possible to solve problems otherwise unsolvable

* It is easy to integrate with our applications. * It supports most commonly used languages such as JavaScript, Python, Php, nodejs, among others. * Easy monitoring of errors in real time with a detailed and accurate description * External Integrations: GitHub, Bitbucket, Trello, Slack, and anothers more

* Some errors are not our application * Email notification can be overwhelming.

I helped to improve the response time in resolving errors as well as in correcting errors in all environments (development, production).

pretty easy to set up. i used a self-hosted version and didn't have much trouble installing it. i love not receiving 5000 emails for one 500 error but just see in sentry that the same issue occurred 5000 times. and to be able to categorize them and mark as resolved.

i think install process can be even simpler.

i have various clients that have various websites. before webapps were just sending 500 emails to email group aka [email protected] which would spam 5 people with many many emails. it's very annoying and creates too much noise. most people just set up email filters so those emails bypass inbox and no one is aware of issues. sentry solves that probles easily, dashboard is awesome too.

error playback! When encountering a bug but there's no way to re-create it. It is primarily the issue. Sentry simplifies it and allows us to do just that. One can monitor the behaviour of the error and most likely will find a solution faster than manual labour.

Added overhead in the production system along with installation. Almost all major framework have their error handling mechanism in place. And they're getting good day by day. So if you're a startup and run a smaller workload, I think you will be better off using native error handling.

Sentry takes the beta tester role and provides rich information regarding the origin, how to reproduce and possible solutions in the context of any given error that may surface.

Helpful in monitoring and notification when we have failures in Production / non-Production environments. Pin-point a component and line of code as the potential cause of failure. Saves trouble-shooting time for the engineering team.

Very difficult to filter the error. Also, not muting repetitive errors causes a lot of extra noise.

Tracking production user failures.

Very easy to monitor any application Support to send custom exception and event data Support to put alerts on tags

Paid plan is pricier for a largish volumne

Sentry is solving for exception tracking and moving into application performance tracking comprehensiviely. We can monitor a lot of our code using it's features and route them to notify to diff destinations

It is easy to install and integrate with multiple languages and platforms. The dashboards and integrations with other systems (Jira, OpsGenie, Slack, etc.) make it easy to integrate into existing developer workflows.

The stack traces and debug information for languages outside of Python are not as detailed as some other platforms. Rate limits and pricing are painful to navigate at times.

Knowing when our applications have issues before customers report them to us. Also, giving us increased confidence to deploy knowing we will be alerted if users are encountering errors.

1. Bug tracking with detailed analysis make life easy for developers 2. Custom Logs which are traditionally stored in files, can now be easily handled with sentry

1. Integration with the major cloud data warehouses is not present like AWS RedShift 2. API integration to import data into analytics portal like PowerBI is not present

1. Integration with different analytics portals and cloud warehouses, so that all the bugs data from the different environments can be collated at one place. 2. API integration so that bugs data can be imported into the local systems for analysis.

Very fast and easy to on-board. Takes less then 5 minutes to get started and seeing it in action. The context provided by event trail is very helpful.

Nothing really. The developer offering is well featured and can be integrated with solution in minutes.

I don't have to reply on my application users to report errors and provide details. Ability to see the event trail, detailed error messages make debugging a whole lot easier.

Great amount of detail for each error. Super easy for me to put numbers to issues in the software.

I, personally, was never able to correlate errors to specific actions. I think there might've been something messed up in our configuration that line numbers were off (some documentation pointed to potential causes).

We had no visibility into what javascript console errors were happening for our clients. This gave us some of that.

The integration of releases and the caught exceptions is fantastic; it can mark exceptions as resolved automatically when a release occurs. I've got it integrated with a Python back-end and a Javascript front-end; setup was straightforward and simple. It will email when new exceptions occur but it can also do other things like post the exception information into a specific Slack channel.

I've had trouble getting Sentry to filter out exceptions that occur during development. These clutter up the display, making it a bit more difficult to find the real errors. Some of the programmer documentation could be better; it was a bit difficult to find some of the configuration settings for Python.

Tracking exceptions that the users of our website experience so that we can find and fix them.

Sentry helps me to identify, examine and diagnose the errors in real time environment as it is really fast in gathering the required information which is needed to diagnose the error. The best part is that I can decide myself on what to do when an error occurs in my app. I can either fix that error or I can roll back to a previous stable version of my app whenever anything unexpected happens. This makes my app stable in its live version throughout the year. It shows the actual stack traces for the error as well as the error’s parameters and online session info to solve the issue quickly.

You need to be extra vigilant while choosing the email notifications from Sentry. If you have not filtered your notifications regarding error messages, it will send you notifications for every single piece of error in your app whether it is of importance or not. Also I feel that the price is a little higher at $29 per month.

Sentry helps me in knowing what’s actually making my app break down, how often is it happening and which users are getting affected by the breakdown. Thus, it provides a detailed and thorough analysis about any crash or break down through Email and SMS notifications. This analysis makes it easy for me to catch the bugs in my application in real time.

Sentry is a great tool to keep track of bugs that occur in production environments. It has API libraries for most of the popular languages out there. Having the possibility to use this for front-end and back-end code is really useful, you just gotta use the specific library for it, for example their Javascript library if you're using it in front-end apps, and their Python library if you're using that in the back-end. Bugs are tracked per project, so there is no problem if you're working in multiple projects at a time.

There's not much that I could say I dislike about Sentry, but there's always room for improvement. For instance, there's room for improvement in the look and feel, and organization of information in the Sentry's UI to view and manage your bugs.

Bug tracking for apps running in a production environment. Even if you follow a very careful process to release software, bugs will always be there. And having a tool that could track these, and have them reviewed as they arise, has innumerable benefits.

A single error reporting platform for almost every popular stack/language we need, pretty easy to integrate. We're using Sentry for our projects with Django, AngularJS, Android ... and it does its job. The service integrations (Slack, github, heroku, ..) are handy and easy to setup as well, plug it into our current workflow and start playing with it in no time. Stable, UX is good overall, with a bunch of useful features from a true error management platform. Sometime we even use it as a mini Jira for our quick clean sessions, and it works great that way. Finally, it's opensource and free on github, for you to grab and setup your own, even make your own forked version, this seems to make Sentry an active product with active development.

Manual installation ain't that super straight forward, but not really bad, probably they encourage us to buy the SaaS paid version instead, but that would be fair enough. With the SaaS version, the price is a bit high at the moment, IMHO.

Tracking bug in all environments, for all applications in our projects. It's much like letting users to become software QA without them knowing it, and you can see the detailed stacktrace/logs in just one place, getting 'em filtered, analyzed etc .. before hand. It's kinda handy and efficient.