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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

1st class MCP server integration. Being able to delegate everything clearly to claude makes life so much easier when it comes to debugging and building context to fix issues. Review collected by and hosted on G2.com.

I think the web app UI is just a bit too "busy". Sometimes take a little while to get to where i need to be to (however this is no longer really an issue as their MCP makes life easy now) Review collected by and hosted on G2.com.

What I like most about Sentry is its real-time error tracking with detailed stack traces and user context, which makes debugging much faster.

The issue grouping and alerting system reduces noise and helps me focus only on critical problems.

Performance monitoring and tracing have been especially valuable for identifying slow APIs and bottlenecks in production.

Release tracking also helps quickly pinpoint which deployment introduced an issue.

Overall, it has significantly reduced debugging time and improved the reliability of our applications. Review collected by and hosted on G2.com.

One downside of Sentry is that the UI can feel a bit overwhelming, especially when navigating between issues, performance, and releases.

Issue grouping is helpful, but it sometimes groups unrelated errors or splits similar ones, which can add extra manual effort.

Alert configuration can also be tricky, occasionally leading to noisy or duplicate notifications.

Additionally, performance monitoring and advanced features can become expensive at scale.

Improving UI simplicity, smarter grouping, and more intuitive alert controls would make the experience better. Review collected by and hosted on G2.com.

Easy visibility into application errors, logs, and success metrics in one place with Sentry. The dashboards are intuitive and flexible, making data visualization simple and actionable. I also like the customizable widgets, which is useful for analytics. Dashboards load efficiently and make it easy to monitor system health in near real-time. ROI becomes more evident as usage scales across monitoring and analytics needs. Documentation is helpful for getting started with basic use cases. Sentry integrates smoothly into our existing stack and was straightforward to set up. Sentry is actively evolving by integrating with AI agents (like Cursor), which adds a new layer of automation to debugging and monitoring. Review collected by and hosted on G2.com.

Auto-refresh for logs is sometimes unreliable, which disrupts real-time debugging. I also see occasional delays and inconsistencies in real-time data across dashboards, making it harder to trust what I’m seeing at a glance. Some advanced features (like MCP/AI integrations) don’t have clear, guided documentation, so it takes extra effort to figure out how to use them effectively. Alerting can also create a lot of noise without more fine-tuned controls. Review collected by and hosted on G2.com.

What stands out most about Sentry is its real-time error tracking and detailed debugging insights, which make identifying and fixing issues much faster. Its performance monitoring helps understand application bottlenecks clearly. I also like the clean UI and integrations with many tools, making it easy to fit into existing workflows. Overall, it significantly improves development efficiency and reliability. Review collected by and hosted on G2.com.

One drawback of Sentry is that its pricing can become quite expensive as usage scales, especially for smaller teams. The initial setup and configuration can also feel complex for beginners. Additionally, the volume of alerts can sometimes be overwhelming without proper tuning. Lastly, some advanced features have a learning curve that may slow down onboarding. Review collected by and hosted on G2.com.

I love how Sentry quickly helps identify and fix issues with detailed stack traces and context. The real-time alerts and session replay make debugging much faster and more efficient. It integrates well with GitHub, Slack, Jira, and Datadog to streamline debugging, collaboration, and issue resolution. I find Sentry’s initial setup quick and straightforward, allowing basic error tracking to start seeing errors in minutes. Review collected by and hosted on G2.com.

With Sentry, a few things could be improved: It can create too many alerts/noise, making it hard to focus on critical issues without tuning. Pricing can scale quickly with higher event volume, which may become costly. The UI can feel complex, especially when trying to quickly find specific insights. Review collected by and hosted on G2.com.

I have been using Sentry for error and performance monitoring for a long time now, and I find it extremely valuable as it makes application errors, crashes and even performance issues visible, allowing teams to fix bugs as soon as they appear in production. I like the context it gives and the trigger and resolution flows. When a new issue appears in production, developers usually have all the information they need to identify the root cause, out of the box. A standout feature for me is the smart grouping of issues, which hugely reduces production noise. Without smart grouping or correct configuration, the same type of issue would appear as different issues, cluttering the Sentry dashboard and any connected methods for delivering alerts. The default initial setup is super easy, and setting up options like tracing is generally easy too. I've integrated Sentry with GitHub, Slack, and email, which works well for my needs. Review collected by and hosted on G2.com.

Recently, they have been adding many new features. While many are valuable, the UI has changed a few times, not always for the better: there are many sections now and sometimes it's not obvious where to find things. Docs are good, but they can always be improved for certain frameworks or can be confusing around releases and health setup. Review collected by and hosted on G2.com.

I like how Sentry gives clear, real-time insight into what's going wrong in an application. The detailed stack traces and helpful context make debugging much faster and more precise. I appreciate the real-time error tracking feature that shows exactly where an issue happened, what caused it, and the context around it, which saves me time and reduces frustration. I use Sentry to monitor performance, identify slow areas, and receive alerts when issues occur, which improves reliability and user experience by catching and fixing problems quickly. It's also great how Sentry integrates well with GitHub, Slack, Jira, and Datadog, which streamlines debugging, collaboration, and issue resolution. Review collected by and hosted on G2.com.

One thing that could be improved in Sentry is the noise from too many alerts, especially in larger applications where minor or repeated issues can flood the dashboard. It sometimes takes effort to fine-tune filters and rules to focus only on what really matters. Managing alert noise can be challenging, but using the right rules helps a lot. However, Sentry could improve by offering smarter prioritization, better default alert settings, and a more user-friendly way to configure filters. Review collected by and hosted on G2.com.

I like that Sentry is easy to use and easy to set up. It makes handling multiple apps with different languages and frameworks a piece of cake. I appreciate not having to worry about breaking parts of a deployment when setting up monitoring, as Sentry doesn't create that issue. The initial setup was very easy, which was a relief. Overall, it keeps my mind away from production servers by ensuring I get notified when there's an issue. Review collected by and hosted on G2.com.

Log search is not always great and many times issues search are difficult to match some errors. Log search would be great if it listed all fields like Splunk does. Issues search would be great if I can search inside the backtrace, URL, or any field without needing to specify them. Many times I know a term for search but I can’t find them with the search. Review collected by and hosted on G2.com.

I appreciate Sentry's tools for collecting telemetry, usage analytics, and detailed information about my software. The well-documented onboarding guides made it easy to add these capabilities quickly, without much thought, and the language-specific integrations automatically collected many data points, saving me the hassle of manual instrumentation. Sentry's accessible approach allowed me to quickly implement telemetry functionalities, which were incredibly helpful for triaging and debugging edge-cases noticed by end-users. I genuinely value Sentry's customer service; reaching qualified support personnel without delay is a standout feature. I found the Session Replay feature excellent for my use-case, as it allows me to watch the exact steps a user performed in a session, making it easier to pinpoint issues. Implementing Sentry's modules in JavaScript and Rust client applications was surprisingly easy, thanks to the step-by-step Getting Started guides, which provided all the necessary code to start collecting analytics. Review collected by and hosted on G2.com.

Based on my tech stack, deeper integrations with Google's Firebase suite would be awesome, including auto-instrumentation and additional info in Tracing. Numerical, countable metrics were also something I missed when I started using Sentry's solutions, however to my knowledge, their new Metrics feature is approaching release soon. Most views on the main interface lack mobile-friendly scaling, I think, UI could be improved a bit when displayed on smaller displays. Review collected by and hosted on G2.com.