It is really good to have Business Process Monitor for being proactive with monitoring critical business services. And it is even more recommended along with APM. However, you will still need some training in order to configure them as they are sophisticated tools.
Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,
Great web interface. Lots of data available in a really clean format, with filtering options and more.
Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
Very generous free tier – 10,000 events per month. We're nowhere near that yet.
It depends heavily on Vugen so it would be great to give more courses on writing scripts in the Business Process Monitor trainings.
When issues arise, we don't have insights into if the issue is from the script itself or if it is a real issue. Here you lose trust in determining which is right until you interfere personally. As an example, one day I got an alert from a business server and the issue was that the script didn't finish successfully and thus it kept the session opened. So the next schedule of the script will fail, not because there is a real issue on the business service, but because you need to go yourself open the application, close all pages, then log out so that the script will continue to monitor.
We used Rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people in company where not able to understand Rollbar dashboard who were very much used to Sentry.
We had to take it down later due to internal reasons and majorly because of cost-cutting process
If someone has a unstable system and have no way to figure out what to do, can use sentry at least temporarily along with some other APM to fix their system faster
