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.

Right now, Sentry meets our needs and we have not encountered any bottlenecks. However, additional personalization and easier setup for capturing all the different application logs could be an area of improvement. Integrations or single sign-on capability with Microsoft would be beneficial for securing all assets.

We have been using Sentry for about six months.

We have not experienced any stability or performance issues with Sentry.

We have not encountered any scalability issues with Sentry. It has been easy to use and configure across multiple systems, each having several environments. It's easy to identify where particular errors occur within different environments.

We have not contacted their technical support because everything is easy to set up under Sentry.

Positive

We previously used New Relic but moved to Sentry because it supports Azure Web Services, which New Relic did not. Additionally, the cost of Sentry is cheaper than New Relic.

The installation of Sentry is straightforward, with good documentation and a step-by-step guide that any technical person can follow. It includes a wizard that outlines the required steps, including the necessary code for the application.

Sentry is very affordable. We spend less than $200 to $300 a month. Compared to New Relic, it provides the necessary features at a cheaper cost, especially since we moved infrastructure monitoring to Azure.

We have not yet utilized AI integration on Sentry as the current volume of logs and the complexity of issues are manageable by our developers. There could be potential for AI integration with future projects. Overall, I give Sentry a rating of 10.

Can you please describe a few use cases for Sentry? What do you use it for?

Thank you so much for that. To sum it up, what are the main benefits that you have seen from using Sentry or how it helps to improve the way your organization functions?

What do you find valuable about Sentry? What are the best features in it from your perspective? And why do you find them valuable?

Can you tell me more about the performance monitoring aspect? How would you describe the benefits of Sentry's performance monitoring in optimizing application speed?

What would you like to see improved or enhanced in Sentry in the future?

Are there any specific features that you would like to see included in the next releases of Sentry?

Overall, regarding the performance and stability of Sentry, have you had any downtimes, crashes, lag in stability issues with it?

When it comes to the scalability aspect, do you find it scalable?

Do you know anything about the technical support or customer service team of Sentry? Have you escalated any questions to them?

Neutral

Can we discuss which product you used before Sentry?

Were you involved in the initial setup of Sentry when it was introduced to your workflows?

Do you know anything about the pricing aspect, the licensing costs, setup cost of Sentry product?

What other options did you evaluate before you decided to go with Sentry?

Were there any disadvantages or cons of Sentry in comparison to other available solutions in the market?

Based on your experience, is there any advice or recommendation that you may share with other organizations considering Sentry for their environment? Should they keep anything in mind before choosing Sentry? On a scale of 1-10, this solution was rated as a 7.

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.

It would be nice if the product provided a map showing the users’ geographic location.

I started using the solution a couple of days ago. I'm using the online platform.

The tool was down for a few seconds today. The stability must be improved. I rate the stability a seven out of ten.

Setting up dashboards and queries in Azure Monitor was the most difficult task. Azure Monitor’s error logging is not as clear as Sentry’s.

I am using the solution on the cloud. I did not deploy anything. It is more cost-effective to use the cloud solution. If we deploy the tool, someone has to manage the infrastructure.

The product costs $26 a month if we choose a yearly subscription. Code coverage can be added for an additional $29 per month. The Team plan is the cheapest package available. We can make our own bundles considering the amount of data and the amount of errors we need to record. We can adjust the price a little bit based on our needs. We don't have to select from the prebuilt business package. If we need more replays, we can ask for extra replays and only pay for that. The pricing seems flexible.

I would recommend the solution to others. It is a straightforward tool. We cannot afford someone spending a lot of time making a monitoring solution. We want something that just works and gives us really good input without having to waste a lot of time. The product gave me nice input. Overall, I rate the product a nine out of ten.

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.

I have not worked with Sentry long enough to provide advice for improvements. I need more experience and time.

I have been using Sentry for about three months. My manager asked me to learn it for future needs.

I would rate the stability of Sentry as eight out of ten, although I do not have extensive experience.

I would rate the scalability of Sentry as eight out of ten. I do not have many years of experience to provide a better answer.

If there are issues, I report them to my manager, who contacts support. My manager receives answers promptly.

Neutral

The implementation is easy. After one or two days, I can learn and use it. It's not too hard.

Overall, I would rate Sentry as an eight out of ten.

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.

To deal with its shortcomings, Sentry needs to continuously improve in areas like the user interface and documentation, apart from its other features.

I have experience with Sentry for two years. I use the free version of the solution.

Sentry is a pretty stable product. It is up to how you handle the exceptions in your application. It has always been about how smartly you are able to leverage Sentry rather than how stable Sentry is, so I feel it's a stable product, and it's always up to the engineer to make use of its stability.

I cannot comment on Sentry's ability to scale up since I did not get much into its scalability part.

Scalability was never an issue in Sentry since we never had to update anything stating that the solution was taking up too many resources in our company. I feel that Sentry's scalability is good.

In our company, we don't require technical support for Sentry. Sentry's documentation is pretty straightforward and neat.

Sentry is a product we use to the bare minimum in our company. Sentry is just a product where we catch exceptions while trying to get some meaning out of it, which was helpful for us, and because of this, we believe it is a really good tool.

I was not involved in the setup phase of Sentry since it was already present in our company's systems and was already a part of our ETL pipeline. I just figured out what Sentry does in my organization and how it needs to be used rather than trying to figure out where and why it needs to be used.

We don't require anyone to maintain the solution in our company. In our company, we used to create projects with Sentry and then use the key in our pipeline. Everyone using Sentry in my company is involved in the maintenance part since it is a product used for a specific project. The person managing the ETL pipelines also helps maintain the solution since that person has his or her project key in Sentry.

To those planning to use the solution, I would say that one of the mandatory things to be included when building a mutual pipeline, and based on my experience, I would say that there will always be the need for applications like Sentry to give you complete coverage. People must use a solution like Sentry to stabilize the pipelines.

Sentry has played an important role by helping me at work, and I feel it should be a part of the ETL pipeline.

I rate the overall solution a nine out of ten.

Our primary use case for this solution is web application monitoring and providing developers access to live error logs, error tracing, and some metrics without providing them real-time production access. So it's a great visibility tool for the developer team.

We find the feature of cause-stack information integrated with the Git repository valuable, which provides contextual information. So, for example, if a line was faulty or triggered an error, it identifies the SQL query that had been run or what values the variables in that context had. Hence, the context and insight it provides about the errors are vital features.

The settings for an administrator are complex. For example, the distinction between teams and the global Sentry settings needs to be clarified where the boundaries are. Also, from the administrative perspective, the UX experience should be improved visually.

We have been using the solution for seven years and are currently using the latest version.

The solution is stable.

The solution is scalable. We had no issues with it.

We have not needed to contact customer service and support.

The initial setup from the UI perspective is not difficult. The default settings work well from the administrative perspective. For example, from the DevOps perspective, they need to set it up as an application on the server side. They found some challenges and part of Sentry is Kafka, an event message queue. Kafka and Zookeeper manage Kafka as the core part of Sentry, administering these parts and not filling up the hard drives with the event-tracing data. Hence, they are some challenges with it. From the UI perspective, I rate the initial setup process a ten out of ten. From a system administrator standpoint, I rate it a four out of ten.

We set it up in-house in our infrastructure, and two or three internal system administrators manage it.

We did not need to pay for licensing because we used the open-source version.

I rate the solution a ten out of ten. The solution is good, but the UX experience could be improved.

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.

Tracking error logs is a great feature because Sentry provides a rich context with regards to the code and tracing issues across the entire stack with trace logs and things like that. It's great at capturing application performance metrics and error logs, things of that nature.

Sentry is more like an application mind trying APM platforms as opposed to also tracking analytics and things like that. It would be nice to have one solution as opposed to using two or three different solutions. I'd like to see user metric tracking, and the ability to create more dashboards for exactly what you want to monitor and see. It's already possible but you have to pay more for it. What Sentry lacks are user-tracking elements like traces.

I've been using this solution for 10 months. 

I think it's pretty stable because I think we have a good review process and because it's open source. Sentry accepts feedback and there's an open-tier version that has a lot of capabilities.

I haven't tried scaling but it's an SaaS product, so I'm betting that it is scalable. We have a development team of 25 who all use the solution and we have one person who deals with maintenance. We're likely to extend use of the solution because we're always trying to capture more metrics and more non-generic data about our applications.

We haven't needed to contact customer service, we just use their documentation which is sufficient for our needs. 

I think the initial setup is pretty straightforward. We configured the agent ourselves. 

I don't really think Sentry's that expensive because there's a lot in the open-source version. Once you fine-tune dashboards and things like that, is when you start thinking about moving to the paid version. 

We looked at Datadog as well, but it was pretty much the same. The difference was that Sentry was a little cheaper because they have the open source option that comes with a lot of features already packed in.

My advice would be to understand what you're trying to monitor in your performance because Sentry can provide a lot of information. I rate this solution nine out of 10. 

I use Sentry to monitor application performance. 

Sentry helps me identify errors in my applications.

Sentry breaks everything down in real time.

It should be easier to integrate Sentry with other tools, and the end-to-end tracing capabilities could be improved. 

I have used Sentry for two years.

Sentry is stable.

Sentry is scalable.

Deploying Sentry is difficult. 

I rate Sentry nine out of 10. 

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.

We cannot restrict particular columns on particular data. It would be helpful if that feature was improved.

I have used Sentry for a year and a half.

It's stable. We haven't had any issues.

It's scalable. We can scale up to a particular limit.

I would rate technical support 3.5 out of 5.

Initial setup is straightforward. We haven't had any major issues. We used three people for installation.

We installed Sentry ourselves. We followed the guidelines provided by Sentry for installation.

We have seen ROI.

I would rate this solution as eight out of ten. 

My advice is to follow Cloudera's guidelines to install Sentry.

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 would like to see the ability to customize events and get more metrics for these customized events. We have another service Kibana from ELK and you can generate charts with your events. In Sentry, you can group events, and you can marry them but you cannot generate customized charts and views based on your events. I also would like to have alert policies and alert conditions enhanced in the next release.

I have been using Sentry for four years.

The stability is very good for Sentry and in general works well. We have forty or fifty engineers.

Scalability is not a problem in my particular use case. We have fifty million users every month.

Since we are using the open-source option the documentation is sufficient for our current needs.

I used Tech Drive when I was working with Google Cloud. I used Prometheus for integration with Grafana to get metrics and we used it as a pulling and a pushing mode to send information from applications to the server of Prometheus. 

The initial setup of a server, I think is alright. It is not very easy, but it is okay.  
If you chose the open-source version, you need a self-hosted server.  In that case, it is more difficult.

I am currently using a self-hosted open version.

I believe the integration of New Relic with alerting software is much better than Sentry.

I would rate Sentry a seven out of ten.