Uploaded byIcinga
Why favour Icinga over Nagios - Rootconf 2015
Icinga is an open-source, scalable, and extensible monitoring system that originated as a fork of Nagios in 2009, with Icinga 2 being released independently in 2014. Unlike Nagios, Icinga 2 is multithreaded, allowing for efficient load distribution and easier feature additions, while also addressing security and architectural limitations. The document promotes Icinga's capabilities and community engagement while highlighting its advantages over Nagios for modern monitoring needs.
More Related Content
Similar to Why favour Icinga over Nagios - Rootconf 2015
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Why favour Icinga over Nagios - Rootconf 2015
- 1. www.icinga.org Why favour Icingaover Nagios rootconf - Bengaluru - 16th May 2015
- 2. • Bernd Erk •Icinga Co-Founder • Project organizer • @gethash
- 3.
- 4.
- 5.
- 6. Open Source EnterpriseMonitoring Icinga is a scalable and extensible monitoring system which checks the availability of your resources, notifies users of outages and provides extensive BI data.
- 7. • Originally forkedfrom Nagios in 2009 • Independent version Icinga 2 since 2014
- 8.
- 9. Icinga Web 2 Icinga2 Icinga Icinga Quality, Testing and Community Support Icinga.org, dev.icinga.org, social media channels Icinga Reports Icinga Doc 3rd Party Tools Icinga Web Icinga Classic (CGI)
- 10. ICINGA 2 -INTRODUCTION
- 11. • Monitors everything •Gathering status • Collect performance data
- 12. • Notifies usingany channel • Considers dependencies • Handles events
- 13. • Checks andforwards logs • Deals with performance data • Provides SLA data
- 14. • Based onC++ and Boost • Supports MySQL and PostgreSQL • Includes a extensive template library
- 15. • Version 2.3.4is out since April • Puppet, Chef and Ansible support • Packages and Vagrant Box available
- 16. WHY NAGIOS™ ISGOOD?
- 17. • Monitoring thingsis easy • Simple software stack • No complex dependencies
- 18. • Active checksare powerful • Huge community • “Millions” of Plugins
- 19. OK, BUT WHYICINGA THEN?
- 20. NAGIOS DOES NOTSCALE
- 21. • It isjust a single loop • Limitations using interfaces
- 22. • Icinga 2is multithreaded • Load is distributed automatically • Monitors in a second interval
- 24.
- 25. # tar -zxvfndoutils-2.0.0.tar.gz # cd ndoutils-2.0.0/ # ./configure CFLAGS=-fPIC # make # make install /usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin /usr/bin/install -c -m 755 -o nagios -g nagios ndo2db-4x /usr/local/nagios/bin/ndo2db /usr/bin/install -c -m 755 -o nagios -g nagios ndomod-4x.o /usr/local/nagios/bin/ndomod.o /usr/bin/install -c -m 774 -o nagios -g nagios file2sock /usr/local/nagios/bin /usr/bin/install -c -m 774 -o nagios -g nagios log2ndo /usr/local/nagios/bin /usr/bin/install -c -m 774 -o nagios -g nagios sockdebug /usr/local/nagios/bin
- 26.
- 27. • We havea powerful CLI • Adding new features is easy • It is simple and could be sophisticated
- 28. # icinga2 featureenable ido-mysql
- 29. NO CLUSTERING ANDDISTRIBUTION
- 30. • No integratedfailover • Configuration is not distributed • No shared monitoring information
- 31. • Availability andscaling zones • Automatic redistribution of checks • Zones for multitenancy environments
- 32. High Availability Checker Notify Gelf Perfdata Graphite IDO Compat Livestatus Checker Notify Gelf PerfdataGraphite IDO Compat Livestatus
- 33.
- 34.
- 35. Advanced Zoning Zone CZoneA Zone B
- 36. SECURITY IS AMESS
- 37. • NSCA works,but not in a good way • NRPE has a couple of security issues • You can make it secure … by hand
- 38. • Bidirectional communicationusing SSL • “binlog” like retention for events • Distributed features
- 39.
- 40.
- 41. define service { host_namelinux1,linux2,linux3,...,linux9 service_description ssh-check }
- 42. apply Service "ssh"{ import "generic-service” check_command = "ssh” assign where host.address && host.vars.os == "Linux” }
- 43. apply Service "ssh"{ import "generic-service” check_command = "ssh” assign where host.address && host.vars.os == "Linux” ignore where host.vars.test == true }
- 44. define hostgroup { hostgroup_namelinux-servers alias Linux Servers members linux1,linux2,linux3 }
- 45. object Host “mysql-server1"{ address = "10.0.0.1“ check_command = "hostalive“ } object HostGroup "mysql-server" { display_name = "MySQL Server“ assign where match("*mysql*", host.name) }
- 46.
- 47. object Service ”webservice"{ import "generic-service” check_command = ”load” host_name = “a really great server” vars.load_wload1 = {{ if (get_time_period(“9to5”).is_inside) { return 40 } else { return 60 } }} }
- 48. • A newconfig format • It is really time for change • You will love it!
- 49. WHAT YOU SEEIS WHAT YOU GET
- 50.
- 54. • Parsing status.datis not really cool • Executing commands is hard • Very inflexible architecture
- 55. • Limitations incurrent Icinga interfaces • Really hard to extend and integrate • No unified interface so far
- 56. • Easy toextend and embed • Multiple authentication providers • Support for db and livestatus • Responsive
- 57. Web 2 Monitoring Docs BPGraphite PNP
- 58.
- 59.
- 60.
- 63. Icinga Camp -Portland 2015 October 10th Icinga Camp - Kuala Lumpur 2015 June 9th
- 64.
- 65.
- 66. Our vision ofintegration
- 67. • Download Icinga2 • Rethink you configuration • Install Icinga Web 2 and play with it • Give us feedback
- 68.