Sentry Reviews & Product Details

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.

Clear, actionable error tracking

Instead of dumping raw logs, Sentry groups similar errors, shows stack traces, and highlights the root cause—so you’re not digging through noise.

Great developer experience

The UI is clean and intuitive, and the setup for most frameworks (JavaScript, Python, etc.) is straightforward. You can get useful insights with minimal configuration.

Real-time alerts that actually matter

It notifies you when something breaks, but with smart grouping so you don’t get spammed with duplicate alerts.

Powerful context & debugging tools

You get breadcrumbs, user sessions, request data, and environment info—basically a replay of what led to the error.

Performance monitoring + tracing

Beyond crashes, it helps track slow transactions and bottlenecks, which is huge for improving user experience.

Integrations that fit dev workflows

Works well with tools like GitHub, Slack, Jira, etc., so issues flow naturally into your existing process. Review collected by and hosted on G2.com.

Self-hosting is not trivial

While it’s open-source, running your own instance of Sentry reliably at scale requires significant infrastructure and maintenance effort. Review collected by and hosted on G2.com.

I really enjoy Sentry's ease of integration, i've worked on a lot different codebases, and Sentry is always very easy to integrate regardless of the architecture.

Recently, i integrated Sentry on a pretty distributed app architecture, and we were able to get traces from React, Node and Rust, and using trace continuation across Typescript, TSX and Rust.

I also use Sentry's notifications on Slack, so i can follow specific labels, for errors on the modules that i'm the owner of. Review collected by and hosted on G2.com.

I think this is user error, but it's very easy to get a noisy Sentry if not configured correctly.

When integration you need mainly uncaught exceptions are logged into sentry, and any important errors, such a specific integration thats key to your app.

I try to avoid having captureException calls around, and having a good architecture that makes it so actual exceptions, DB errors, Library Errors, etc, do make it to the top level. Review collected by and hosted on G2.com.

I really appreciate Sentry's super detailed traces and the information about errors, which are extremely helpful. The error grouping in the 'issues' tab makes it easy to see how often an issue is occurring across our stack and provides all the possible information needed to understand what's happening. I also love how it's connected to Claude Code, allowing the agent to pull all the relevant information and look through the logs for me. This connection is beneficial because debugging would take me 10-20x longer without Claude's help, as it efficiently searches through all of our traces and logs to find patterns in usage and errors. Review collected by and hosted on G2.com.

The logs don't have very good advanced filtering on the UI based on attribute, also there isn't a good API connection to pull the logs from projects. I sometimes have to use MCP with Claude, but the data received isn't always well-organized, leading to confusion. Also, the pricing model/rate limiting is an issue. My bills were extremely high unexpectedly, and I couldn't see the logs I needed until the quota reset. More documentation and advice on minimizing unexpected costs would be helpful. The initial setup was pretty complex and overwhelming, taking me 40 hours to really grasp it, and I still feel I'm not using it to its full capacity. Review collected by and hosted on G2.com.

I like the UI and the UX of the Sentry web app, as it's really nice and modern. It's also quite easy to work with the SDK, which makes integrating and using Sentry straightforward. I’ve used their Discord channel a number of times to reach out to the community for help with issues, and I always get a quick response from Sentry employees there. So I definitely recommend Discord for support. Review collected by and hosted on G2.com.

There were some issues with the logging side of Sentry when we first set it up with the OTLP log drain. We raised the problems in their Discord channel, and while Sentry team members said they had fixed them, I believe we're still experiencing some issues when trying to filter using the filter bar for certain properties in the log messages. It doesn't find the property, so you have to manually expand a log message and go through additional steps to add it to the filter. I've thought this issue would have been fixed by now as it's been quite a number of months. Also, the auto refresh on the logs seems quite slow and not really as smooth as I’d expect. It sometimes stops, and I've got to refresh the page myself. I've stopped using it as often because of this and tend to manually click refresh. Review collected by and hosted on G2.com.

What I like most about Sentry is how easy it was to integrate into our frontend and how quickly we were able to start getting meaningful insights. As a frontend engineer, the real-time error tracking has been especially helpful for debugging issues fast, since it provides clear stack traces along with useful user context. I also appreciate how seamlessly it connects with tools like Slack, which makes it easier to stay on top of new errors as they come in. Review collected by and hosted on G2.com.

One thing I dislike about Sentry is the amount of duplicate or noisy events it can generate. As a frontend engineer, this becomes frustrating because it clutters the dashboard and makes it harder to quickly identify real issues.

It also has a direct impact on cost—since Sentry’s pricing is largely based on event volume, even duplicate or low-value errors can consume your quota and increase billing if you go beyond limits . So without careful filtering on the frontend, you can end up paying for noise. Review collected by and hosted on G2.com.

I appreciate Sentry for how it displays the issues users face and traces errors effectively. It's great that I can see helpful information like how many times an error has occurred and configure the level of detail via tagging. The minimal setup required is definitely a bonus, eliminating much of the headache on my end. I also like how easily it integrates notifications with Slack, with extensive configuration options for sending them with the specific information I need. The ease of use stands out to me, and I found it really easy to set up and plug into other apps. Their AI feature, Seer, is particularly impressive with its accurate initial guesses that help debug confusing errors. The initial setup of Sentry was super easy and quick, taking about an hour. Review collected by and hosted on G2.com.

Some of the setup steps were a little confusing, had to rely on AI to understand what some things meant so I guess the onboarding process could be improved in that regard. I think the guides on what to do after you have stuff setup could be improved. I feel like I really need to dig into the docs to get more use out of the software as it provides a lot of features. Review collected by and hosted on G2.com.

I use Sentry for logging, profiling, and error detection. One major advantage is that it allows us to find and resolve errors much faster, often before customers even notice them. Sentry's logging setup is particularly easy compared to other solutions, which tend to be more difficult and confusing. I like how Sentry's documentation is comprehensive and covers everything I need. This made it easy for me to set up logging and tracing across about 10 micro-services in just two days. The platform itself is intuitive to navigate. I love the unique and fun UI of Sentry. The error tracking is valuable because it provides the complete stack trace, which simplifies problem solving. Additionally, the logging is nearly real-time with only a one-minute delay, which I find impressive. The initial setup was smooth, akin to spreading butter, making the entire adoption seamless. Review collected by and hosted on G2.com.

They have a strict un-changeable 30 day retention period for logs. I would very much like for it to be customizable even if it costs extra. Review collected by and hosted on G2.com.

I really find Sentry helpful for identifying code level bugs through the issues section. It’s great that I can add our app and get warnings and error messages which I can report to the dev team to optimize app performance. The insights and dashboards are also really useful, especially for creating weekly reports. I like that the dashboard provides web page load times with different percentile values, which is important for understanding user impact and improving user experience by reducing loading times. After the initial setup, it became very comfortable to use. Review collected by and hosted on G2.com.

Sentry does not provide insights for video content like video start time and buffer time, making it difficult to analyze video performance. Also, although Sentry tracks page loads, it would be beneficial to have an option to view weekly or monthly uptime for different pages. Review collected by and hosted on G2.com.