Sentry Reviews & Product Details

I use Sentry for application monitoring, log tracking, and issue tracking. The main problem it solves for me is visibility; it allows us to know what's going on in our production instance, giving us insights and data to monitor system health. I find the UI and UX phenomenal—everything you need and nothing you don't. The speed and ease of setup are also awesome. Sentry is simple, clean, and easy to use, with low cognitive overhead. Even non-technical users can navigate the system intuitively. The initial setup was incredibly easy, taking about 15 minutes max. Review collected by and hosted on G2.com.

Dashboarding widgets are sometimes a little unclear and limited. Maybe a how-to guide on how to use them all. Like, how come I can't use big number widgets for the issues dataset? Review collected by and hosted on G2.com.

I use Sentry every day for monitoring mobile and backend in our fintech app, and it works very well for us. I like how it allows us to track every small part of the app. The feature that connects the front end with the backend is particularly helpful because it makes it easy to see an error on the front end and find the corresponding error on the backend. Switching from Bugsnag to Sentry was definitely an improvement for us, and the initial setup was really easy. Review collected by and hosted on G2.com.

There are some interesting features that are paid and we are already paying a lot, that's not a good thing. Review collected by and hosted on G2.com.

The best part is its ability to automatically capture errors with rich context—such as stack traces, user actions, environment details, and release versions—so developers can quickly understand not only what went wrong, but also why it happened. This significantly reduces the time spent trying to reproduce issues.

Another major advantage is the clean, intuitive UI. It groups similar issues together and surfaces the most critical ones, which makes triage much easier. On top of that, features like performance monitoring, release tracking, and alerting make it feel like a comprehensive tool rather than just an error logger. Review collected by and hosted on G2.com.

One drawback of Sentry is that it can sometimes feel overwhelming, especially for new users. The volume of error data and alerts can be high, making it difficult to prioritize issues without proper configuration. Review collected by and hosted on G2.com.

I use Sentry for monitoring our scheduled jobs, tracing errors, and logging purposes. I appreciate the more insight it provides into errors, offering a good stacktrace and making it easy to see the history and number of events or users affected. I like the Session Replays feature, the ability to add breadcrumbs and tags, and the capability to monitor releases. It's easier to add alerts for specific tags, see what end users struggle with, and identify which releases started creating new issues. The setup was pretty straightforward, thanks to the great documentation. Review collected by and hosted on G2.com.

The CRON scheduler can be improved to be able to set alerts based on environments. Right now it alerts on all environments including Development. Provide use the ability to choose multiple environments for CRON monitors. Review collected by and hosted on G2.com.

I like that Sentry's UI is fast and presents a lot of the information clearly and efficiently. The filtering is good and allows us to have logs across all three environments with easy switching between them. The screen layout is efficient, which helps individuals, whether they're a developer or engineer, find the information they need to resolve issues. Additionally, I found the setup process to be really good. Review collected by and hosted on G2.com.

I would ideally like the Lambda logging to include individual requests. At the moment, you can only capture top-level boto3 invocations, where we would move all of our current observability over if we could have more granular control over the request response payloads. Review collected by and hosted on G2.com.

I really appreciate how easy Sentry is to set up right out of the box. It's been straightforward from the beginning, reducing friction to get started. I also like how active they are in adding features. We were early adopters of the logging features, which was especially helpful in bridging gaps in understanding weird behaviors on our devices. It helps us gain visibility and get alerted immediately to any erroneous activities, and allows us to track the performance of the devices, which helps us compare and contrast different device models. Review collected by and hosted on G2.com.

I think their tracing feature lacks some functionalities. For example, it was having random issues and unpredictable on how it was working, I couldn't set up sub spans properly. Yes, make it more feature rich, allow us to have sub spans. Make it easier to hook onto span lifecycles. Review collected by and hosted on G2.com.

I like having a general dashboard for all my apps, with visibility into errors across them and a central place for issues. I also like the level of detail Sentry provides for errors and that I can hide sensitive information like JWTs. Review collected by and hosted on G2.com.

I don't like how easy it is to set Sentry up incorrectly. When that happens, I get too many notifications, and it's hard for me to distinguish useful emails from junk. Review collected by and hosted on G2.com.

I like how easy Sentry is to use and all the integrations it offers, especially with Slack and MCP, which really make identifying errors and assigning them to the right people effortless. The out-of-the-box deep integration and instrumentation with many langauges is great because I can easily add it in and it works perfectly (no need to manually instrument). I also appreciate the smooth integration with PagerDuty, as it ensures we get alerted for important issues. Additionally, working with our AI models, the MCP helps us quickly locate and address bugs. The initial setup was really easy too; getting into the code base and logging events was a breeze. Review collected by and hosted on G2.com.

I think the tracing is a little bit hard to use sometimes. It's a little bit difficult to use the trace viewer compared to something like New Relic, where it's easier to see where the bottlenecks are (ie. DB and distributed tracing).in the the LLM instrumentation, there was a little bit of memory leaks that we noticed inside the Sentry library. It was open source, so we fixed that up ourselves. Review collected by and hosted on G2.com.

I really like Sentry's Slack integration because it helps me get real-time notifications of new issues without having to constantly check the Sentry website. Also, the logs are good for tracking deep inside, especially when a bug appears on a client device. They come in very handy for checking API calls or pages visited around the time of the issue. The seamless integration and ease of use were reasons my team switched to Sentry from Datadog. The initial setup was also very easy with the documentation provided. Review collected by and hosted on G2.com.

I have one suggestion in logs, as when the response of any API is long, it gets truncated. There could be an option to allow users to download the whole response without truncation in JSON format for in-depth analysis. 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.