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
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
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.
