Sensus FlexNet Communications Network vs. Sensu, by Sumo Logic

Sooner or later, companies are going to figure out that there's more to monitoring than what Nagios can provide. For those that want to dip their toe in the water and still provide backward compatibility with a legacy Nagios environment, Sensu is a good choice. It's mainly for businesses that want more than Nagios but don't want to take the full plunge with something radically different and metric-based such as Prometheus. Having moved to metric-based monitoring so far as I'm able, I can say with confidence that it's far better than what Nagios or Sensu provide.

Incentivized

• Unique concept as a "monitoring router" that can tie services together.
• Backward-compatible with Nagios environments.
• More of a DevOps focus than Nagios.

Incentivized

• Cannot be solely used for tracking metrics over time.
• Not a very good UI.

Incentivized

Sensu's customer support was always willing to work with us but never really seemed to learn much from our experiences. I think they get a lot of customers with DevOps IT teams that are willing to put in a lot of elbow grease to get the most of Sensu's architecture. However, despite explaining my continued disappointment with their documentation and the overall flow of the product, I never got much more than a "sorry" and a notice that their documentation was open source if I wanted to contribute to it. The problem, of course, is that you can't document what you don't understand. I'm a former technical writer, so I know that better than most.

Incentivized

Have used New Relic and Sematext Cloud for APM and for tracking over days and visualizing the issues. But those are very expensive as compared to Sensu.

Incentivized

• Can easily understand and extend use-cases to under server capabilities.
• Can use it to scale well.
• Can help in efficient resource planning.

Incentivized