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

• Well suited for raising pagers when you have count-based metrics.
• Well suited for threshold-based metrics.
• Not well suited for tracking events over the day, since graphs and other visualizations are missing.

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

• There are some settings which we can't configure from UI (Web Console).
• We've open[ed] up configuration files in command line text editors and manually do the settings e.g. LDAP/SSO configuration.
• In terms of visualization, it's best, but it doesn't support log analysis otherwise it could destroy business of all other visualization tools.

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

Incentivized

It is infinitely flexible. If you can imagine it, Grafana can almost certainly do it. Usability may be in the eye of the beholder however, as there is time needed to curate the experience and get the dashboards customized to how it makes sense to you. I know one thing they are working on are more templates, based on data sources

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 blows Nagios out of the water when it comes to customization. The ability to feed almost any data source makes it very versatile and the cost is great.

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

• Grafana has replaced many higher priced tools
• The integrations are seemless with multiple backends
• Combining graphs and dashboards from multiple data sources is a game changer

Incentivized

• Standing up the Sensu Go server took very little effort.
• Setting up and maintaining the build processes and deployment logic for Sensu assets and checks was somewhat exhausting and resulted in lower adoption among non-DevOps IT.
• The limited web interface resulted in lower adoption among non-DevOps IT.

Incentivized