
The thing I like most about Sentry is its video replay feature. Whenever Sentry is integrated into my application and the application is deployed, it can capture user-session activity and show developers the relevant part of the session where an error occurred. This allows developers to understand exactly what the user was doing before the error happened, such as which button they clicked or which link they followed. It makes identifying and debugging issues much easier because I can understand the sequence of actions that led to the error instead of relying only on error logs.
Another thing I appreciate is how easy Sentry is to integrate into an application. The setup process is straightforward, and once configured, it continuously monitors the application for errors. Its generous free plan is another major advantage, especially for students, beginners, and developers working on personal projects. Review collected by and hosted on G2.com.
The thing I dislike about Sentry is not its services or functionality but rather its dashboard and user interface. Sentry provides a huge amount of information for every individual error, which can sometimes feel overwhelming, especially for new users.
For example, it displays detailed information such as the user's IP address, device details, error timestamp, root cause, affected files, and other technical data. Although this information is extremely useful for experienced developers, beginners may find it difficult to understand and navigate through so many details at once.
I think Sentry could improve its dashboard by presenting the most important information in a simpler and more organized way, while keeping the advanced technical details available for users who need them. This would make the platform more beginner-friendly without compromising its powerful debugging capabilities. Review collected by and hosted on G2.com.