Icinga vs Sensu: What are the differences?
What is Icinga? A resilient, open source monitoring system. It monitors availability and performance, gives you simple access to relevant data and raises alerts to keep you in the loop. It was originally created as a fork of the Nagios system monitoring application.
What is Sensu? Open source monitoring framework. A monitoring framework that aims to be simple, malleable, and scalable. Essentially, Sensu takes the results of “check” scripts run across many systems, and if certain conditions are met; passes their information to one or more “handlers”. Checks are used, for example, to determine if a service like Apache is up or down.
Icinga and Sensu can be primarily classified as "Monitoring" tools.
Sensu is an open source tool with 2.96K GitHub stars and 389 GitHub forks. Here's a link to Sensu's open source repository on GitHub.
What is Icinga?
What is Sensu?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Icinga?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Icinga?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
One size definitely doesn’t fit all when it comes to open source monitoring solutions, and executing generally understood best practices in the context of unique distributed systems presents all sorts of problems. Megan Anctil, a senior engineer on the Technical Operations team at Slack gave a talk at an O’Reilly Velocity Conference sharing pain points and lessons learned at wrangling known technologies such as Icinga, Graphite, Grafana, and the Elastic Stack to best fit the company’s use cases.
At the time, Slack used a few well-known monitoring tools since it’s Technical Operations team wasn’t large enough to build an in-house solution for all of these. Nor did the team think it’s sustainable to throw money at the problem, given the volume of information processed and the not-insignificant price and rigidity of many vendor solutions. With thousands of servers across multiple regions and millions of metrics and documents being processed and indexed per second, the team had to figure out how to scale these technologies to fit Slack’s needs.
On the backend, they experimented with multiple clusters in both Graphite and ELK, distributed Icinga nodes, and more. At the same time, they’ve tried to build usability into Grafana that reflects the team’s mental models of the system and have found ways to make alerts from Icinga more insightful and actionable.