Sentry Reviews & Product Details

I use Sentry for visibility, traceability, and error detection in my web app. It helps me detect errors before my customers report them, which is useful because there are errors that don't create enough friction for customers to report them. I appreciate that it helps me document my errors thanks to its traces and its connection via MCP, which allows me to analyze bugs with the help of AI agents. I like the replays, as they have helped us gain visibility into errors we didn't know existed and that were never reported by customers. Additionally, I find that the initial setup of Sentry was very easy. Review collected by and hosted on G2.com.

I would like it to have a more user-friendly interface for my customer support staff, as they find it very technical. They have said: 'I can't or don't know how to search for a replay related to a bug reported by a user.' I feel it would be useful for them to group replays by user with their logs and traces, or if this is already done, to make it easier for the user. 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 love the attribute tagging and use Sentry a lot for observability and metrics. I'm able to quickly respond to bugs because of the really helpful trace data. Using attributes to strongly type our logs makes searching through our multi-tenant platform very easy. I also find it great how Sentry integrates with other apps, like Slack. Review collected by and hosted on G2.com.

I really want more visualization tools. I have all these logs but limited ways to show a narrative. From memory, I can only group by a certain amount before the unique groups get clumped together. Because security alert data volume is really important, it means I must leverage different tools to get this data over a time series. 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.

I really like Sentry's documentation, it is very good and well indexed and structured, which makes it easy to change my observation strategy with agility. Additionally, I think Sentry's price is very good and competitive compared to other more expensive tools. The integration with our application framework was quite simple, as the perfect use case was documented and well updated. Sentry also integrates well with other tools we use, such as our Cloud Code and Slack, for issue resolution and receiving alerts. Review collected by and hosted on G2.com.

Yes, what I have already mentioned. I think that traces, at least in NodeJS and TypeScript, sometimes you lose the trace due to the asynchronous nature of Node, which results in orphan traces. I remember this didn't happen to me with Dynam Trace, as it was injected at the container level, while Sentry seems to rely on Open Telemetry, which has its own small inconveniences in TypeScript, which are a bit cumbersome. Review collected by and hosted on G2.com.

Sentry is incredible at cutting through the noise. Instead of sifting through endless logs trying to find what went wrong, Sentry groups related errors together and surfaces the ones that actually matter. The real-time alerting is fast and actionable, and the stack traces with source maps make debugging so much faster. We went from spending hours tracking down production issues to resolving them in minutes. Review collected by and hosted on G2.com.

The pricing can add up quickly once you start hitting higher event volumes, and the alert configuration has a bit of a learning curve to get dialed in without getting spammed. The UI can also feel slightly overwhelming at first with all the features available, but once you know your way around it becomes second nature. Review collected by and hosted on G2.com.

I like that Sentry is trying to base itself on a standard like OpenTelemetry, which makes it easier for us to follow a standard. If we decide to change in the future, the cost would be very low, and that's an advantage. Additionally, the documentation is quite good, which makes it easy to integrate and scale. Review collected by and hosted on G2.com.

Seer should be more agnostic. Also, the mapping for TypeScript with JavaScript doesn't work very well. On the other hand, sometimes spans are lost for certain executions. I would like greater integration with nest.js because although you support it well, I think the way of handling errors only for unhandled exceptions is not correct. The initial configuration was also a bit limited for the level of monitoring we are looking for. Review collected by and hosted on G2.com.

most user friendly,UI is really user friendly and filters are helpful to get my logs exactly which i felt really helpful Review collected by and hosted on G2.com.

Wrong backend logs, i don't know few days back i am trying to deploy to prod in app it is showing 502 but in sentry logs it is showing 200 from backend. I think there is a glitch over there when check the actual pod hits it shows 502 and 200 for other hit. I feel it got mixed up that made me waste sometime. Apart from that it is a great platform Review collected by and hosted on G2.com.