Sentry Reviews

We use Sentry for application performance management and tracking bugs and issues in the application.

One of the greatest advantages of Sentry is its support for Azure Web Services, which New Relic does not support. Sentry integrates with common developer communication platforms like Discord and WhatsApp, which allows developers to easily track notifications and findings in the applications. Real-time error tracking helps our Quality Assurance team easily identify the root causes of problems or bugs and promptly inform the developers about specific issues.

I am exploring Sentry, New Relic, and Azure Monitor. The tools can be used to monitor our solutions. We want to improve the reliability of the applications.

Sentry was easy to learn compared to New Relic and Azure Monitor. I saw some valuable input. It took us the least amount of time to see how Sentry is valuable. It took just a few minutes. Session Replay provides a replay of the recorded errors. It is a good feature. Azure Monitor does not have this feature. The error reporting is straightforward. We can see everything that we need to see. The dashboard seems pretty fine. The product performs well. We can see the user's IP addresses.

I use Sentry to send project errors and find bugs in the project. I work on fixing the bugs, even though some come from external integrations.

I only work with part of Sentry. I know about the simple usage, not very deep, though. At this time, I focus on finding and fixing bugs. In the future, I may need to learn more about other parts, but for now, I do not use all features.

Sentry is a service to which we send all the application alerts, which is like an alert management app.

Sentry plays a very wide role in your ETL pipeline. Apart from the application alerts, there are a few more other things that you need to cover when building your ETL pipeline, including sending metrics, generating logs, and storing them somewhere. For example, if you want to put such data into a warehouse while also being able to handle the exceptions. The exceptions get sent to Sentry, which has its orchestration mechanism of sending alerts to various teams, though it doesn't have an advanced orchestration mechanism, so we would just send an email to the respective teams in our company. Sentry has helped our company detect silent failures in our application site and has helped us many times to handle silent failures.

We are in banking, so we need a lot of protected data. Sentry allows us to restrict users from accessing certain data.

It's deployed on-premises, and we have multiple servers. 

There are eight people in our team, and they all use Sentry. We have another team of six people who are also using it.

We have plans to increase usage in the future.

The most valuable feature is the ability to create and assign rules and give access to particular users.

I use Sentry for internal applications from our front end to our back end code and to capture past services, tracing, calls, and the time it takes to process requests and updates. We're integrating with Gib so from the code base side of things we can trace changes, bottlenecks, etc. I'm a senior software engineer.

The solution has enabled us to improve our request processing which has resulted in a huge improvement in productivity and turnaround time for fixing bugs and the like.

My primary use case has been in front-end and in back-end applications. 

The most valuable feature I have found is how easy grouping events is. 

I use Sentry to monitor application performance. 

Sentry helps me identify errors in my applications.