Icinga vs. Prometheus vs. Sensu, by Sumo Logic

Icinga is a world-class monitoring system. It can be used for most general monitoring situations. It is not a silver bullet, however, and there are instances where domain-specific monitoring systems are necessary. However, the output from those monitoring systems can be funneled into Icinga as a central monitoring and alerting system.

Incentivized

This program works from the roots of the problem and creates a professional matrix for each of its users. This will give them more skills and resources to carry out tasks and reduce the difficulties of operating each of the processes of my work, as well as being An ally for the manipulation and operability of all your master data; Prometheus is very easy to recommend since it is a program that fulfills its mission.

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

• Wealth of community-developed plugins.
• Stable codebase.
• Icinga 2 supports distributed monitoring.
• Very performant, can support tens of thousands of checks per server.

Incentivized

• Looking at metrics such as the aggregate number of HTTP requests served.
• Understanding how our services are performing in aggregate.
• Easy to deploy within a variety of architectures/environments.
• Open source so new features are added regularly and bugs are fixed in a timely manner.
• Free so there are no licensing restrictions.
• Endorsed by the Cloud Native Computing Foundation.

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

• High learning curve, setting up Icinga from scratch can be a bit of a challenge starting out.
• If the io2db process fails you UI stops updating, which can be very frustrating.
• There is no simple mechanism for adding new hosts and services through the web UI, it's all very config-file based.

Incentivized

• Customer Service: since this is an open-source tool, customer service is not that great. Generally, you get all answers to your problems in online forums, but in case you got stuck, nobody will assist you in a channelised manner. You will have to find the way out on your own, and it may become frustrating at times.
• More metrics for dashboards shall be added per the application being monitored. Standards metrics will work in most cases but may not in specific applications. Therefore, customised metrics shall be created for some of the industry-standard niche applications.

Incentivized

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

Incentivized

Icinga is a solid solution which does everything it promises. It is backwards compatible with most Nagios instances, making the transition very easy. Once you get the hang of installing new plugins and editing configuration files expanding its monitoring capabilities are easy.

Incentivized

It is usable and one can learn if few people in the team are already using it. It can be difficult to understand at the beginning because of non intuitive UI and syntax of the rules. So, I've gone for 7 points as there is some room for improvement in user interface and rules syntax.

Incentivized

Never had to reach out to them.

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

Icinga is better than Nagios because of its nicer user interface. New Relic can monitor CPU/memory and disk usage, but it's more of a performance and application troubleshooting tool rather than monitoring

Incentivized

Highly customized pricing plans to choose from. Lower pricing for the same features compared to competitors. Easy to reach the support team, which provided detailed documentation and helped set up the Prometheus. Monitoring metrics gets very easy after the integration with Grafana. It also has a sophisticated alert setting mechanism to ensure we don't miss anything critical.

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

• With one check you know which applications are faulty e.g. after an upgrade. Which is big time saver
• You easily detect outages ion the applications so that your customer ideally does not even realize there was an outage.
• Detect if the environment does deliver the same result as in the same time as before to detect shortages.
• Additional information when debugging. Saved us several hours where we could simply point to a database which was slow.

Incentivized

• We are still working on the ROI
• The ROI mentioned during the purchase has not been achieved, however this could be due to lack of data from our side. 2 years of implementation is too early to calculate and confirm the ROI.

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