Grafana vs. Sensu, by Sumo Logic

Just about any organization with more than one server and more than one cluster as it scales very well. Configuration of the application takes time and finesse to fine tune to where the balance of load time and getting data quickly meets. The plugins add load time but fine tuning for the application to meet demand needs nailed down at implementation

Incentivized

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

• Alerting through many different medium as Slack, Email, Webhook etc
• Beautiful and unlimited number of dashboards to view your metrics and tweak them as you please
• Log aggregation and powerful Logql to filter and view your logs
• Microservices monitoring
• Large number of plugins and data sources to collect your metrics from almost anywhere

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

• Documentation needs to be more clarified since it can be confusing for beginners
• Notification alert message templates need to be simplified

Incentivized

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

Incentivized

Great usage in terms of monitoring of any application from backend to frontend and even any AWS resource via cloud watch and other connectors. Easy to use and configure personalised dash boarding and alerting features. Cost efficient and easy to setup and run, no mazor scaling challenges in terms of managing and maintaining the stack, easy to configure via Prometheus, influx and other connectors

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

Grafana is more flexible, readily adopts other tools frameworks instead of forcing you to use their agent, doesn't force you into Vendor lock-in, and embraces open source, self-hosted, and Enterprise. Similar companies would like you to use their specific tooling and don't offer nearly as much flexibility. The other thing I like about Grafana is their storage usage is much lower compared to similar tools and competitors

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

• It has kicked out some of our paid monitoring and visualization tools.
• Now Monitoring, Visualization and Alerting is being done in a single platform.
• It made monitoring and visualization very easy for us.

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

Incentivized