Sentry helps me most when a business user reports an issue. Our users are worldwide, and their reports are often hard to follow because they use their own functional jargon and details get lost in translation. Because we send the user’s login name as a tag on every event, I can filter Sentry on that user and pinpoint the errors behind their report without fully decoding what they wrote. That saves me a lot of back-and-forth and time. It’s even easier now that I can combine Sentry with AI through the Sentry MCP, which helps me analyze and correlate those errors faster. Review collected by and hosted on G2.com.

The main downside is the amount of setup work needed to get real value out of Sentry. Out of the box it captures errors, but to make them useful you have to configure a lot yourself: deciding which tags and context to send (for example the user’s login name on every event), keeping them consistent across services, and tuning grouping, alerts and noise filtering. It took us a fair amount of time and iteration to get this right, and it’s easy to end up with incomplete or inconsistent data if you miss something. Review collected by and hosted on G2.com.