Why favour Icinga over Nagios?
summary
Compares Nagios and Icinga by outlining long-standing problems in Nagios, highlights differences between Nagios and Icinga, and describes how Icinga 2 can simplify monitoring for both small and large environments.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:20originally forked from Nagios in 2009 • focus on improvements and scalability • independent version Icinga 2 since 2014 web interfaces and addons
- 5:24monitors everything • in a regular interval preferring active checks gathering status • collect performance data / metrics
- 7:46Icinga 2 release 2.3.8 (2015-07-20) • new code base on C++ and Boost similar ideas to Nagios • Puppet, Chef and Ansible integration • Packages and Vagrant Box available
- 10:17Nagios™ is good, because: active checks are powerful gathering performance data huge community thousands of Plugins
- 12:20Icinga wants to be open community support everything we do 100% free software contributions welcome
- 13:01Nagios does not scale * it's just a single loop limitations using external interfaces x large installations are difficult
- 14:52Icinga 2 on the other hand provides a multithreaded engine distributes load in cluster automatically is able to monitor thousands of devices every few seconds
- 21:50How about high available Nagios? x there is no integrated failover mechanism x configuration is not distributed x no shared monitoring information
- 22:45What Icinga 2 provides you ✓ zones for multitenancy environments support for logic splits in the config availability and scaling zones automatic redistribution of checks master / satellite / agent
- 27:32Icinga 2 clustering is PKI TLS only bidirectional connections helps you setting up a CA replication of events and status
- 41:12Using commands safe against shell injections clean interface, easy to write just set a var in service or host check our ITL template library
