G2

Gorav A.

Catalog Management Executive

Mid-Market (51-1000 emp.)

10/31/2026

"All our errors in one place, but the feed gets noisy"

4/5

What do you like best about Sentry?

What I like best is having errors from all our products in one feed. Our website, mobile app, Node server and partner portal all report into Sentry, so when something breaks I can see it straight away with the level, how many events and users are affected, when it was first and last seen, and the trend over the last 24 hours or 14 days. The stack traces and the URL or screen where the error happened make it much easier to tell whether an issue is a real problem for users, like 503s on search pages or app crashes, or just noise. Filters by project, environment and status, plus saved views, help me focus on unresolved issues that matter. I also like that it connects to our other tools, so I can pull issues into my AI assistant and Slack to investigate and share them without copying screenshots around. Review collected by and hosted on G2.com.

What do you dislike about Sentry?

The feed can get noisy. Some issues have been "ongoing" for months or even years, such as recurring 503s, chunk load errors and browser-specific warnings, and they sit next to genuinely new problems, so it takes effort to separate what needs action from background noise. Setting up good alert rules, issue grouping and ignore filters to cut this down takes time and isn't very intuitive for someone who isn't a developer. The interface is also quite dense, with lots of tabs, views and terms that are clear to engineers but harder for analysts or product people to follow. Finally, because pricing is tied to event volume, a sudden spike in errors can use up a lot of quota quickly, so we have to keep an eye on usage. Review collected by and hosted on G2.com.

What problems is Sentry solving and how is that benefiting you?

Before Sentry, we often found out about bugs only when a user complained or when a drop showed up in our funnel metrics, and then it was hard to tell whether the cause was tracking, traffic or an actual error on the site. Now errors on our website, app and backend show up in Sentry as they happen, with the affected page, device and number of users. When I investigate a drop in leads or bookings, I can quickly check whether there was a spike in errors, such as failed API requests or app crashes, during the same period, which saves a lot of guesswork. It also gives our developers a clear issue with a stack trace to fix instead of a vague bug report, so problems get resolved faster. Overall it helps us catch issues before they hurt conversions and makes it much quicker to rule errors in or out during root cause analysis, which easily justifies the cost. Review collected by and hosted on G2.com.