Sentry Recensies & Productdetails

quicker intigration is the best when i thought of seting it up

repeated notification but it is a valuable feature

quicker integration, website and app crash monitoring

- Detailed Error Reporting - Session Replay feature is awesome gives proper error reporting with user session recording - User Management is better - Multi Project support is good - Alert feature is good

- Give less session replay in the first plan. - some times UI un-responsive while using session replay

- Error reporting and Alerting. We will get the issue and fix it before the user reporting to us - Session replay allow us to get proper error reporting

What I like about Sentry is that it is easy to install in your project so you can start getting the errors immediately. It has a lot of metrics, and helpful information to help you debug better.

I have nothing to say about this. Sentry is very lovely, it has a generous free tier, and as a student, you can use it for many projects and a lot of reports without any cost.

Sentry benefits me by collecting the failures in the system I've built independently so I can debug errors and fix them with insightful information stored in their nice UI.

The ability to trace errors and get the complete stack trace when an error is thrown in the backend application of my company. Easy monitoring and filtering through to debug and make changes in code. Near-real time uploading of logs is a must when production grade apps are deployed

Probably a more enhanced UI can help with better dashboards, web components to perform macros on the web app. Better customer service response should make this a must-recommend product

Error logging, debugging javascript errors, making changes in code, sharing a monitoring space with multiple developers, one source of truth for logging errors and understanding issues in the app

What I like most about Sentry is its ability to detect and capture errors in real-time, the detailed information it provides about the root cause of errors, the ability to customize and configure alerts, and the flexibility to adapt to specific monitoring needs.

I don't like that certain features of Sentry are not available in the plan you are using, or that the price is a bit high for the budget, or that the integration with other development tools is not as seamless as I would like.

Sentry has allowed me and my team to monitor the logs in real-time and quickly detect any problems that may arise. This has helped me to identify the root cause of errors and fix them, thus improving our systems and applications.

One of the best things about Sentry is its ability to provide detailed information about errors and exceptions in real-time. This allows developers to quickly identify and diagnose issues, which can save them a lot of time and effort in the long run.

Some users may find that Sentry has a relatively steep learning curve, especially if they are new to error tracking and monitoring tools. Additionally, while Sentry is an open-source tool, some of its advanced features and integrations are only available in the paid plans.

Sentry solves several problems for developers and organizations, which can ultimately benefit their users and customers. Some of the key problems that Sentry addresses include: 1. Error tracking and monitoring: Sentry allows developers to track errors, exceptions, and other issues in real-time, which helps them identify and diagnose problems quickly. 2. Performance monitoring: Sentry also provides insights into the performance of applications, which can help developers optimize their code and improve the user experience. 3. Collaboration and communication: Sentry integrates with various tools and platforms, such as GitHub and Slack, which can help teams collaborate more effectively and resolve issues faster. 4. Debugging: Sentry provides detailed information about the source and context of each error, which can help developers debug their code more efficiently.

Group of the logs and showing up the spikes

sometimes the loading of the logs take much time

It helps in monitoring the logs and the unknown sentries

The ease of setting it up in a React Native project.

Sentry can slow your app in the dev environment

It helps us identify CRASHES and Application Performance in a better way when compared to Firebase.

Sentry offers a plethora of features, namely error tracing. When an error occurs your get a lovely stack trace, details about what platform it happened on and much more. On top of that, they offer APM so you can use telemetry to speed up your api calls. They offer tons of tools for frontend too but I've mostly only worked with backend errors and apm. Pricing is great.

There's not much to dislike. A lot is plug and play and the docs are beautiful. If I had to pick on thing, I'd say overages of your monthly alllowance of errors could be pushed more. i.e "Make sure to set limits so you don't go over your monthly limits for errors or APM"

Sentry was able to help catch tons of unexpected issues with great detail and context. It also helped speed up a ton of API calls being able to see query and cache usage in the APM dashboard

The ease of use, and the quality and level of details in error reporting, through its integration with django, redis and celery. Performance module is also very useful to monitor the overall performance of our app in production

It's kind of tricky to get detailed info/documentation for integrations on the on-premise version of sentry.

Error reporting in production and application performance monitoring

Really simple tooling for most languages and frameworks

UI can be a little confusing to navigate sometimes

Sentry captures errors and metadata around those errors so that they can be triaged and patched

Sentry does a great job of exposing errors in your application and, perhaps more importantly, makes it really easy to track down and debug the errors. It also integrates well with your git hosting client to let you know when you introduce a regression and exactly what release it came from.

The interface can be somewhat noisy. There is a lot of information, which is great, but it clutters the screen and it can just be a lot to process, especially when you first start using sentry.

We use sentry to monitor all of our client websites and applications. It has been saved our developers a ton of time when trying to debug issues. It has also been really useful of notifying us when errors occur so we can take care of them before the client even knows there was an issue. It truly has been a game-changer for our business.

very easy to implement in new or existing software products. very well documents for all the variety of the languages.

should contain more easy way to log some other stuff than bugs

capture error traces for every host in our data flow. also, capture what the client sends us in advance to reproduce but and investigate them quickly.

Not provided

Not provided

Not provided

For web products, It's incredibly easy to configure and with a simple integration you can start to track your product. The information it attaches with a default configuration to every issue helps a lot with bug fixing and debugging, something that can be enhanced providing stack traces, suspect commits or even session replay. It does offer a lot of options to also enrich the events with custom information or tags that can be helpful for more precisely debugging.

The integration with web apps is quite simple, but it lacks a lot of features it offers with another frameworks like release health or more rich metrics. The stack traces can be confusing sometimes, but I guess it depends of your build configuration and stack.

We need to monitor an international web app that can be executed in a very diverse environment (devices, OS, browsers...) where sometimes strange errors can happen. Sentry helps us to react to unexpected issues in production as well as to better identify corner cases and to know the real impact of some issues in our web apps audience.

Very quick install with just some lines of code. Much easy to get notifications across email, messages, or chat as part of a present workflow when mistakes occur or resurface. I like that error tracking system which is built for community.

Nothing to say bad about that software. As for me and my working team, we like every step of the working process. We never had problems with the tracking system.

We can make better sorting, reproduce and solved errors with maximum performance and appearance. We have the ability to exception handling with this platform helps developers make better apps and repeat quicker.

We've been using Sentry as an error reporting tool. The performance is great where one can expect timely alerts for all the events triggered across servers. The traceback can be easily understood and one can get to the problem very easily.

There can be better filters for notifications, otherwise one can get bombarded with emails.

We wanted to catch bugs early on and sentry does a great job. It reports front-end JS errors and my backend php errors with complete stacktrace which makes it very easy to fix them.

Sentry has error handling clients written for almost every technology that our company uses. In addition to the Python and JavaScript client libraries, they have additional libraries that plug right into common development frameworks like Tornado, Django, Angular, etc. Installation of these client libraries is amazingly simple.

There is a lack of embeddable widgets on error metrics. We'd like to make it easy for us to create/share/export a generic dashboard and/or graph to view all stats (not just Sentry). That being said, they do have an API that allows the end user to fetch the error events (so that you can plot them on your own).

This helps us maintain uptime (especially on new deploys). Keeping track of new, occurring, and regressing errors helps our engineering team prioritize what to work on.

Sentry is extremely fast at gathering all the information necessary to debug an exception. It also groups them into accurate categories and provides permalinks to each error for reference. I always make sure that, when I start a new project, I get the Sentry project access key and integrate Sentry right away. Without it, I feel blind when I am debugging errors on our servers.

The search feature could be better. You can't always construct the exact search that you want, narrowing down to a specific error message at a specific time on a specific host accessed via a specific path. You can usually get there by browsing and filtering, so it's a minor nitpick.

I am a developer on a medium-to-large team and use Sentry for debugging errors in our API that serves our mobile apps. The main benefit of having Sentry is an indexed and searchable error log to quickly find and reference recurring exceptions.

- Multi-language support: allows us to track our Python and Javascript errors with a single product - Ease of settings in the web interface: limits domains, notifications frequency - Possibility to track all events: messages, exceptions, etc. - Two offers: SaaS (not free but all is managed for you) or instable on your own server for free - Integration with Trello, to pass information through our different SaaS

- No way to filter/categorize elements in the interface to filter events after in the main list (except by assignation to people...). It is possible to set tags only when the event is fired... - Javascript errors catched are sometimes not our concerns (e.g. Skype plugin or third party bug) - No sandbox to test configuration before deploying in production

Mostly bugs in production and have a better communication about it: we notify people who have encounter problems once bugs are solved. Customers says we are pretty reactive on this point and Sentry is a big help in this. Also help us to reproduce bugs thanks to context user data like browser or inputs done.