Sentry Reviews & Product Details

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.

I find Sentry's error tracking and logs really useful. The recent release of their log product is a game changer for us because we can tie that directly to errors and quickly query any logs and related errors to understand what's going on inside our application. The main thing I value is the MCP server. We use the error tracking and logs more than anything else, and Sentry integrates well with kind of the traces and metrics. It usually provides really good detailed feedback because of the instrumentation set up inside of Sentry. Review collected by and hosted on G2.com.

The only thing I can think of is that it's just a pretty heavy package. Uploading, like, the source maps and stuff takes a little bit of time. It's just heavy because of that stuff. It's also a little bit unavoidable because of everything that they're doing. There's an HTTP API that's super powerful, but then an MCP server that's kind of okay, and also a CLI that's kind of okay. I would like one or the other, either CLI or MCP, to be super powerful and be the direct source where I can get everything in one central location. Review collected by and hosted on G2.com.

I like the logging and profiling features of Sentry because they help me track my application's usage status in real-time. These features tell me whether the application is working fine, up to mark, and if any latency or slowness is experienced by my users. They help me identify the reason for any latency, giving me a clear picture of what's happening on the platform. The initial setup was very simple, which I appreciated. Review collected by and hosted on G2.com.

I guess, they should work upon , if I want to keep my logs for a longer period of time, then there should be a kind of provision so that I can configure that. I can keep my logs in the sentry for a longer period of time because sometimes these are needed for my introspection. Review collected by and hosted on G2.com.

I like that Sentry integrates well with other places. For example, we get Slack notifications, and it makes feedback more accessible than having to check the platform itself. It also integrates well with our AI tooling to debug issues more easily. I appreciate that the information doesn't just stay inside of Sentry but can be accessed from other tools I use day to day, which means I don't have to actively check up on the platform. Review collected by and hosted on G2.com.

For me, it's sometimes quite a complex product. That's partly because I'm more focused on the frontend than back-end, so sometimes the amount of information is not super easy to grasp. Review collected by and hosted on G2.com.

I appreciate that Sentry has become an indispensable part of our stack over the last 3+ years across multiple projects. The SDKs are well-designed and integrate with popular frameworks in minutes, making setup pretty easy. Once running, the error reports and stack traces are detailed and contextualized, which makes it easier to reproduce and fix bugs quickly. The alerting system is flexible enough to surface issues that really matter without overwhelming the team. Additionally, the performance monitoring dashboards provide a clear picture of where bottlenecks occur in real-time, helping to catch them before users notice. Review collected by and hosted on G2.com.

Pricing scales up quickly at higher event volumes, documentation can be outdated for advanced configs, and log management lacks depth compared to dedicated logging platforms. Review collected by and hosted on G2.com.