I like that Sentry is easy to use and easy to set up. It makes handling multiple apps with different languages and frameworks a piece of cake. I appreciate not having to worry about breaking parts of a deployment when setting up monitoring, as Sentry doesn't create that issue. The initial setup was very easy, which was a relief. Overall, it keeps my mind away from production servers by ensuring I get notified when there's an issue. Review collected by and hosted on G2.com.

Log search is not always great and many times issues search are difficult to match some errors. Log search would be great if it listed all fields like Splunk does. Issues search would be great if I can search inside the backtrace, URL, or any field without needing to specify them. Many times I know a term for search but I can’t find them with the search. Review collected by and hosted on G2.com.

I appreciate Sentry's tools for collecting telemetry, usage analytics, and detailed information about my software. The well-documented onboarding guides made it easy to add these capabilities quickly, without much thought, and the language-specific integrations automatically collected many data points, saving me the hassle of manual instrumentation. Sentry's accessible approach allowed me to quickly implement telemetry functionalities, which were incredibly helpful for triaging and debugging edge-cases noticed by end-users. I genuinely value Sentry's customer service; reaching qualified support personnel without delay is a standout feature. I found the Session Replay feature excellent for my use-case, as it allows me to watch the exact steps a user performed in a session, making it easier to pinpoint issues. Implementing Sentry's modules in JavaScript and Rust client applications was surprisingly easy, thanks to the step-by-step Getting Started guides, which provided all the necessary code to start collecting analytics. Review collected by and hosted on G2.com.

Based on my tech stack, deeper integrations with Google's Firebase suite would be awesome, including auto-instrumentation and additional info in Tracing. Numerical, countable metrics were also something I missed when I started using Sentry's solutions, however to my knowledge, their new Metrics feature is approaching release soon. Most views on the main interface lack mobile-friendly scaling, I think, UI could be improved a bit when displayed on smaller displays. Review collected by and hosted on G2.com.

I find Sentry's error tracking and logs really useful. The recent release of their log product is a game changer for us because we can tie that directly to errors and quickly query any logs and related errors to understand what's going on inside our application. The main thing I value is the MCP server. We use the error tracking and logs more than anything else, and Sentry integrates well with kind of the traces and metrics. It usually provides really good detailed feedback because of the instrumentation set up inside of Sentry. Review collected by and hosted on G2.com.

The only thing I can think of is that it's just a pretty heavy package. Uploading, like, the source maps and stuff takes a little bit of time. It's just heavy because of that stuff. It's also a little bit unavoidable because of everything that they're doing. There's an HTTP API that's super powerful, but then an MCP server that's kind of okay, and also a CLI that's kind of okay. I would like one or the other, either CLI or MCP, to be super powerful and be the direct source where I can get everything in one central location. Review collected by and hosted on G2.com.

I like the logging and profiling features of Sentry because they help me track my application's usage status in real-time. These features tell me whether the application is working fine, up to mark, and if any latency or slowness is experienced by my users. They help me identify the reason for any latency, giving me a clear picture of what's happening on the platform. The initial setup was very simple, which I appreciated. Review collected by and hosted on G2.com.

I guess, they should work upon , if I want to keep my logs for a longer period of time, then there should be a kind of provision so that I can configure that. I can keep my logs in the sentry for a longer period of time because sometimes these are needed for my introspection. Review collected by and hosted on G2.com.

I like that Sentry integrates well with other places. For example, we get Slack notifications, and it makes feedback more accessible than having to check the platform itself. It also integrates well with our AI tooling to debug issues more easily. I appreciate that the information doesn't just stay inside of Sentry but can be accessed from other tools I use day to day, which means I don't have to actively check up on the platform. Review collected by and hosted on G2.com.

For me, it's sometimes quite a complex product. That's partly because I'm more focused on the frontend than back-end, so sometimes the amount of information is not super easy to grasp. Review collected by and hosted on G2.com.

I appreciate that Sentry has become an indispensable part of our stack over the last 3+ years across multiple projects. The SDKs are well-designed and integrate with popular frameworks in minutes, making setup pretty easy. Once running, the error reports and stack traces are detailed and contextualized, which makes it easier to reproduce and fix bugs quickly. The alerting system is flexible enough to surface issues that really matter without overwhelming the team. Additionally, the performance monitoring dashboards provide a clear picture of where bottlenecks occur in real-time, helping to catch them before users notice. Review collected by and hosted on G2.com.

Pricing scales up quickly at higher event volumes, documentation can be outdated for advanced configs, and log management lacks depth compared to dedicated logging platforms. Review collected by and hosted on G2.com.

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.