Sentry is quick to set up and offers excellent developer tools. I really appreciate its proactive email notifications they help us catch issues early. The UI could use some improvements, but overall it's a great product and has been a game changer for our app. Review collected by and hosted on G2.com.

My only complaint is that some parts of the interface can feel cluttered, making it take longer to find certain settings. Aside from that, the product works really well. Review collected by and hosted on G2.com.

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

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

I really like the web UI in terms of usabilty.

Also, I noticed that performance is really great.

Other thing really important for us is that Sentry have an integration with Slack, this will be really helpfull.

I found the onboarding process very quick and clear. I work as a QA and I understood it well. However, it might be better to have an onboarding process focused exclusively on QA. Review collected by and hosted on G2.com.

I haven't used the tool much to get a complete understanding of it.

However, I've heard from some other people that Sentry could have:

Post-deploy regression analysis

After each deployment, automatically generate a report:

- new errors;

- slower endpoints;

- degraded functionalities;

- comparison with the previous version

I don't know if this is actually not already available, but it would be a great addition to the tool. Review collected by and hosted on G2.com.

UI is okay-ish, not super intuitive at start and felt a bit confusing with too much data, but once I got used to it it actually became pretty helpful and finding errors is easy. integrations are solid, setup was simple and it just works with our RPA stuff without much effort. performance has been good, errors come almost real time and didn’t notice any slowdown. pricing sometimes feels a bit high but it saves a lot of debugging time so overall worth it. onboarding was decent, docs were enough and didn’t really need much support. AI/intelligence side like error grouping is useful, avoids getting spammed with same issues again and again, not using heavy AI features but whatever is there does the job. Review collected by and hosted on G2.com.

what I don’t like much is the UI widgets, they feel a bit confusing and not very consistent, sometimes hard to quickly understand what I’m looking at. also auto refresh doesn’t work properly many times, I still have to manually refresh to see latest errors which is annoying. and sometimes issue grouping is not accurate, same type of errors show up as separate issues which makes things a bit messy to track. Review collected by and hosted on G2.com.

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.

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.

Another benefit I didn’t expect at first is Sentry’s performance monitoring. In addition to error tracking, it gives clear visibility into slow transactions and bottlenecks, which helps improve overall application performance and the user experience. Overall, Sentry has reduced troubleshooting time, strengthened incident response, and increased my confidence in the reliability of our applications. Review collected by and hosted on G2.com.

While Sentry is a powerful monitoring tool, one drawback is that the sheer volume of alerts can sometimes become overwhelming, especially in large applications with frequent events. It often takes time to fine-tune alert rules and issue grouping so you can cut down on noise and stay focused on the most important problems.

Another area that could be improved is the learning curve around some advanced features, such as performance monitoring, custom dashboards, and more complex alert configurations. New users may need extra time to fully understand these options and use them effectively.

Additionally, investigating issues across multiple projects can occasionally feel cumbersome, and some advanced features are only available in higher-tier plans. Even with these limitations, the benefits of faster error detection and troubleshooting still outweigh the challenges for me. Review collected by and hosted on G2.com.

Sentry allows us to (for the most part) centralize all our diagnostic data in a single place. We depend heavily on AWS infrastructure and services, and migrating away from Cloudwatch has truly been an illuminating experience on how much of a non-product that is when it comes to observability. Review collected by and hosted on G2.com.

While our adoption is still in the early stages, the biggest issue we’ve run into so far is the lack of OpenTelemetry Metrics support. Review collected by and hosted on G2.com.

UI / UX

The interface took me a little while to get used to, but once I did, it felt pretty intuitive. The issue dashboard is well-organized and grouping similar errors together saves a ton of time. I especially like how clicking into an error gives you everything in one place — stack trace, breadcrumbs, user context — without jumping between tabs.

Integrations

This is where Sentry really shines for me. It plugged into my GitHub and Slack setup without any hassle. The GitHub integration is particularly useful — it links errors directly to commits and even suggests which code change likely caused the issue. That alone has saved me hours. Review collected by and hosted on G2.com.

Pricing / ROI

Honestly, the free tier starts feeling limiting pretty quickly once your project grows. The event quota runs out faster than I expected, and when it does, you either start losing error data or you're forced to upgrade. The jump in pricing between tiers felt a bit steep for an indie developer or a small team watching their budget. I also wish the quota system was a bit more transparent — it took me some time to fully understand what counts as an "event" and how fast I'd burn through my allowance. That said, if you're at a company with a proper engineering budget, it's probably not a dealbreaker. Review collected by and hosted on G2.com.

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.

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.

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.

The GitHub integration is especially valuable. By linking our repositories, Sentry ties each error back to the source, including the suspect commit, the file, and the relevant code, along with the surrounding application details. This significantly shortens the time it takes to identify a root cause and assign the right owner, since we are not guessing where a problem originates.

Sentry helps us monitor the health and uptime of our applications effectively. We get visibility into errors as they happen across web, mobile, and backend services, so we can catch regressions early, keep an eye on stability after each release, and respond before issues affect more of our users.

We also use AI, Sentry Seer to surface likely root causes and propose code-level fixes, which speeds up debugging. Review collected by and hosted on G2.com.

I think the pricing can be cheaper. And I think it will be good if we can filter spends without upgrading to business plan. Review collected by and hosted on G2.com.

Sentry gives me the full picture of what's happening in my app at any given time. The UI makes it easy to navigate — error grouping, stack traces, and breadcrumbs are laid out in a way that actually makes sense. When something breaks, I'm not left guessing: it pinpoints exactly where things went wrong and why, down to the specific line of code.

The integration with Next.js and our CI/CD pipeline was straightforward, and performance monitoring has helped us catch bottlenecks we wouldn't have noticed otherwise. The AI-assisted issue triage is a nice touch too — it helps prioritize what actually needs attention. It's the kind of tool that makes you wonder how you ever shipped software without it. Review collected by and hosted on G2.com.

The initial setup and configuration can take some time to get right, especially when fine-tuning alert thresholds to avoid noise. Review collected by and hosted on G2.com.

Sentry has become the industry standard for error tracking because it shifts the focus from "something is wrong" to "here is exactly how to fix it."

The "magic" of Sentry lies in its ability to provide a timeline of events leading up to a crash. It captures:

Breadcrumbs: A trail of user actions (clicks, navigation, API calls) that occurred right before the error.

Session Replay: A video-like reproduction of the user's screen, allowing you to see exactly what they saw without asking them for a screenshot.

Stack Traces: Direct links to the specific line of code in your GitHub or GitLab repository that caused the failure Review collected by and hosted on G2.com.

Duplicate Issues: Sometimes slight variations in a stack trace (like different line numbers in different versions) cause Sentry to treat the same bug as two separate issues, leading to duplicate notifications. Review collected by and hosted on G2.com.