Sentry Reviews

What do you like best about Sentry?We really saw the value of the full stack when an ASP.NET Core release introduced a regression that only affected customers with a specific configuration. The first sign was a slight uptick in 500 errors—noticeable, but not enough to trigger our usual infrastructure alerts. In Sentry, the exceptions were grouped in a way that made the pattern clear: the affected users shared the same feature flag and the same release. From the issue, we opened the trace and could see the request spending far longer than expected in a SQL call before it ultimately failed. Suspect Commit then narrowed our search even further by pointing us to the refactor where configuration loading had changed, which gave us a much smaller area to investigate. After we shipped the fix, we used Application Metrics to confirm the error rate returned to baseline, rather than assuming the incident was resolved just because the deployment completed successfully. We also realized our original alert was too sensitive and kept notifying on transient failures, so we replaced it with a Monitor that accounted for both rate and volume. Sentry didn’t eliminate the debugging work, but it did put the error, trace, release, and user impact on a single investigation path. That reduced the time we normally spend correlating logs across services and gave us a much better way to prove the fix actually worked in production.What do you dislike about Sentry?The combination of Tracing, Logs, and Application Metrics is what moved Sentry beyond basic error monitoring for us. Since the .NET SDK began supporting metrics and Application Metrics became generally available, we’ve been able to track counters, gauges, and distributions, break them down by attributes like region or plan, and then pivot from an anomaly straight into the related trace, log, or error—without having to manually line up timestamps across multiple systems. We ran into this recently when auth failures started creeping up. The metric made the trend obvious, but the real value was being able to jump into the affected requests and see exactly where the failure was occurring. Monitors & Alerts have also become easier to manage because the signal and the notification path can be handled separately. A threshold can create an issue with the right context, while Slack, email, or PagerDuty routing is maintained independently. That separation helped us eliminate several duplicated alert rules that had slowly accumulated across projects. Cross-Event Querying is another feature I’m using more during technical reviews now, not only after incidents. Being able to search across spans, logs, and metrics makes it much easier to investigate a suspicious pattern early, before it turns into something urgent. The API improvements around traces, profiles, and attachments have also been helpful when we want to pull parts of that investigation into our own internal tooling, rather than forcing every workflow through the dashboard.Recommendations to others considering Sentry?Sentry has grown into a much bigger product than it was a few years ago. Issues, Explore, Traces, Logs, Metrics, Profiles, Releases, Monitors, and Seer add a lot of depth, but that breadth can also feel disorienting for a developer who opens the platform simply trying to understand a single exception. I’d prefer the initial experience to adapt more clearly to the task at hand, rather than immediately exposing the entire observability surface.What problems is Sentry solving and how is that benefiting you?We really saw the value of the full stack when an ASP.NET Core release introduced a regression that only affected customers with a specific configuration. The first sign was a slight uptick in 500 errors—noticeable, but not enough to trigger our usual infrastructure alerts. In Sentry, the exceptions were grouped in a way that made the pattern clear: the affected users shared the same feature flag and the same release. From the issue, we opened the trace and could see the request spending far longer than expected in a SQL call before it ultimately failed. Suspect Commit then narrowed our search even further by pointing us to the refactor where configuration loading had changed, which gave us a much smaller area to investigate. After we shipped the fix, we used Application Metrics to confirm the error rate returned to baseline, rather than assuming the incident was resolved just because the deployment completed successfully. We also realized our original alert was too sensitive and kept notifying on transient failures, so we replaced it with a Monitor that accounted for both rate and volume. Sentry didn’t eliminate the debugging work, but it did put the error, trace, release, and user impact on a single investigation path. That reduced the time we normally spend correlating logs across services and gave us a much better way to prove the fix actually worked in production.

What do you like best about Sentry?Sentry makes it easier to find and fix bugs; everything is clean and fast in that software.What do you dislike about Sentry?It feels a bit confusing at first and sometimes shows too many things when you're solving the main problem.What problems is Sentry solving and how is that benefiting you?Sentry helps us detect errors while the app is running, and for me, it helps detect issues faster while the app is running.

What do you like best about Sentry?What I like most about Sentry is how effectively it helps me identify and fix issues in real time. Its error tracking is very thorough, with clear stack traces, helpful context, and visibility into user impact, which makes debugging much faster. The performance monitoring and alerts also make it easier to catch problems early, before they affect too many users. Overall, it saves developers a lot of time and helps improve application reliability.What do you dislike about Sentry?One downside of Sentry is that it can feel somewhat complex to set up and fully configure, especially for beginners. The interface is powerful, but it can also be overwhelming at times when you’re trying to navigate issues, filters, and all the available options. Pricing can also become expensive as usage scales, which may be a concern for smaller teams or startups. On top of that, fine-tuning alerts can be tricky, and if you’re not careful with the configuration, it’s easy to end up with too many notifications.Recommendations to others considering Sentry?Sentry addresses the common problem of not knowing when—and why—applications break in real-world usage. Without it, errors can easily go unnoticed or be difficult to reproduce, which slows down debugging and negatively affects the user experience. What problems is Sentry solving and how is that benefiting you?

What do you like best about Sentry?Sentry has grown from a basic error-reporting tool into an indispensable “intelligence layer” that genuinely changes how a development team operates. Instead of relying on static logs, it acts like a “black box” flight recorder for applications. Features like Session Replay and Breadcrumbs let me see the exact sequence of user actions leading up to a crash, which removes the usual “can’t reproduce” dead end and saves hours of manual debugging every week. What do you dislike about Sentry? Recommendations to others considering Sentry?In 2026, the addition of the Seer AI agent has taken this a step further. Rather than spending time digging through stack traces, I can lean on the AI to correlate latency spikes with specific code deployments and even suggest automated fixes directly via GitHub. It creates a proactive workflow where the system can flag the “suspect commit” and route it to the responsible developer before a single user report ever reaches the support desk. What problems is Sentry solving and how is that benefiting you?

What do you like best about Sentry?What I like most about Sentry is its real-time error monitoring and the detailed stack traces, which make it straightforward to pinpoint the root cause and fix issues quickly. The dashboard feels clean and is easy to navigate, and features such as performance monitoring and issue grouping help cut down on troubleshooting time. Overall, it improves application reliability by helping developers spot problems sooner and resolve them faster.What do you dislike about Sentry?One thing I dislike about Sentry is that the initial setup and alert tuning can take a fair amount of time, especially for larger applications. The volume of error data can also feel overwhelming at times, and some of the more advanced features are only available on higher-tier plans. I also think better customization options for dashboards and notifications would improve the overall experience.What problems is Sentry solving and how is that benefiting you?Sentry helps us quickly identify, track, and diagnose application errors before they have a significant impact on users. With real-time alerts, detailed error reports, and performance insights, it cuts down the time we spend debugging and helps us resolve issues faster. As a result, our applications are more stable, downtime is minimized, and we can deliver a better overall experience for users.

What do you like best about Sentry?I use Sentry mainly for tracking application errors and monitoring performance, and it helps me quickly identify bugs by showing detailed error logs, stack traces, and user context. I like how Sentry gives complete and clear error details in one place, showing exactly where and why an error happened in the code, making debugging very fast and efficient. I appreciate the real-time alerts that indicate when something breaks and help in identifying performance bottlenecks like slow API calls or pages. Integrating Sentry with tools like Slack for instant error alerts and GitHub to link errors directly with commits is beneficial. Switching to Sentry from basic logging tools improved our error tracking and monitoring, making it more efficient and organized.What do you dislike about Sentry?Some things in Sentry could be improved. The initial setup can be a bit confusing and sometimes it sends too many notifications if not configured properly. Also, for larger projects, the pricing can feel a bit high.What problems is Sentry solving and how is that benefiting you?I use Sentry to track application errors and monitor performance, quickly identifying bugs with detailed error logs and stack traces. It sends real-time alerts for issues and identifies performance bottlenecks like slow API calls, making debugging fast and efficient.

What do you like best about Sentry?What I like most about Sentry is its real-time error monitoring and the depth of its debugging insights. It automatically captures exceptions, stack traces, and performance issues, which makes it much easier to pinpoint the root cause of problems without spending hours manually digging through logs. What do you dislike about Sentry? Recommendations to others considering Sentry?A feature I rely on often is the error grouping and alerting system. It helps me prioritize critical issues and cuts down on noise from duplicate errors. This has noticeably improved our workflow by keeping the focus on high-impact fixes, resolving problems faster, and minimizing application downtime. What problems is Sentry solving and how is that benefiting you?

What do you like best about Sentry?Performance Monitoring and Tracing are two features I use almost every day. They've helped me catch slow database queries, API endpoints that are slowing things down, and performance issues I probably wouldn't find by looking at logs alone. Error Monitoring is still the feature I rely on the most. Instead of getting a generic error message, I immediately have the stack trace, browser, environment, app version, affected user, breadcrumbs, and pretty much everything I need to start debugging. There's a lot of information available, but it's organized well enough that I can usually find what matters in just a couple of minutes. I also like where Sentry is going with features like Cron Monitoring and Feature Flags. I find myself using more of the platform over time because everything fits together really well.What do you dislike about Sentry?Some of the more advanced features, especially around distributed tracing, performance profiling, and full observability, do take a little time to get used to. It's not that they're difficult, but it takes a while to understand how everything fits together. After a few weeks of using them, I definitely get a lot more value out of the platform than I do during those first few days.What problems is Sentry solving and how is that benefiting you?After every major release, there's always that moment where you're waiting to see if something unexpected slips through. No matter how many tests pass, real users always find scenarios you never thought about during development. That's exactly what happened on one of our recent deployments. We started seeing a handful of errors that looked like they might be related, mostly affecting a browser nobody on the team used regularly. Instead of waiting for support tickets to pile up, I jumped into Sentry. What really impressed me was using Seer AI. It quickly summarized what was happening, grouped the related issues together, and pointed me toward the events that were most likely coming from the same root cause. I still verified everything myself before touching production, but it got me to the right part of the code much faster than I would've on my own. Between the stack traces, session context, performance data, and Seer AI's summary, I had everything I needed to prepare a fix that same day. By the next deployment, the issue was already resolved.

What do you like best about Sentry?It helps us identify backend bugs in both new and existing features, and it improves our overall system efficiency.What do you dislike about Sentry?There isn’t anything we dislike about it.What problems is Sentry solving and how is that benefiting you?Overall system stability and monitoring and bug resolution.

What do you like best about Sentry?We use Sentry for Work for error monitoring and application health, and it has become a core part of how we build and maintain our products. What do you dislike about Sentry?One of the things I value most is the ability to create unlimited projects. This lets us give each application and service its own dedicated space instead of mixing everything together, which keeps errors properly scoped so each team sees only what is relevant to them and can triage without noise from unrelated services. Recommendations to others considering Sentry? What problems is Sentry solving and how is that benefiting you?The user interface is genuinely intuitive. Everything is laid out clearly, so anyone on the team can jump in, find an issue, understand its impact, and start investigating without much hand-holding. Setup is straightforward too, and it does not carry the steep learning curve we have experienced with other tools, so new projects and new team members can be onboarded quickly.