As I said before, not only for Spectrum, but for any monitoring tool, you need to know what is critical in your environment and think about how exactly you should monitor and treat it. If you have done that, everything will work just fine.
Well Suited - Networking Monitoring
Less Appropriate - When you need to customize some monitoring and to update the version
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.
Other tools I have used are more server/application-centric. CA Spectrum seems to work effectively and efficiently for network devices. Notification delays can be set to grant grace periods in case of network blips or false positives, which occur ALL the time. Other monitoring tools send event notifications immediately and would clear instantly, which while on-call can wake a technician for no reason.
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