Keynote at the second day of RootConf in Bangalore organised by HasGeek. Talk deals with the major Icinga2 advantages compared to Nagios

1. www.icinga.org
Why favour Icinga over Nagios
rootconf - Bengaluru - 16th May 2015

2. • Bernd Erk
• Icinga Co-Founder
• Project organizer
• @gethash

3. Thank You

4. THE ICINGA PROJECT

5. Quick Poll

6. Open Source Enterprise Monitoring
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 forked from Nagios in 2009
• Independent version Icinga 2 since 2014

8. You?

9. Icinga Web 2
Icinga 2
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 using any channel
• Considers dependencies
• Handles events

13. • Checks and forwards logs
• Deals with performance data
• Provides SLA data

14. • Based on C++ and Boost
• Supports MySQL and PostgreSQL
• Includes a extensive template library

15. • Version 2.3.4 is out since April
• Puppet, Chef and Ansible support
• Packages and Vagrant Box available

16. WHY NAGIOS™ IS GOOD?

17. • Monitoring things is easy
• Simple software stack
• No complex dependencies

18. • Active checks are powerful
• Huge community
• “Millions” of Plugins

19. OK, BUT WHY ICINGA THEN?

20. NAGIOS DOES NOT SCALE

21. • It is just a single loop
• Limitations using interfaces

22. • Icinga 2 is multithreaded
• Load is distributed automatically
• Monitors in a second interval

24. ADDING MODULES IS HARD

25. # tar -zxvf ndoutils-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. Checker
Notify
Gelf
Perfdata Graphite
IDO
Compat
Livestatus

27. • We have a powerful CLI
• Adding new features is easy
• It is simple and could be sophisticated

28. # icinga2 feature enable ido-mysql

29. NO CLUSTERING AND DISTRIBUTION

30. • No integrated failover
• Configuration is not distributed
• No shared monitoring information

31. • Availability and scaling zones
• Automatic redistribution of checks
• Zones for multitenancy environments

32. High Availability
Checker
Notify
Gelf
Perfdata Graphite
IDO
Compat
Livestatus
Checker
Notify
Gelf
Perfdata Graphite
IDO
Compat
Livestatus

33. Checker
Notify
Perfdata
Gelf IDO
Graphite
Compat
Livestatus
Distributed Features

34. Zone A
Zoning
Zone B

35. Advanced Zoning
Zone CZone A Zone B

36. SECURITY IS A MESS

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 communication using SSL
• “binlog” like retention for events
• Distributed features

39. Graphite
Notify
Gelf
Perfdata Checker
IDO
Compat
Livestatus
Checker CheckerChecker Checker

40. CONFIGURATION LIMITS

41. define service {
host_name linux1,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_name linux-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. ONE MORE THING …

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 new config format
• It is really time for change
• You will love it!

49. WHAT YOU SEE IS WHAT YOU
GET

50. HOPEFULLY NOT!

54. • Parsing status.dat is not really cool
• Executing commands is hard
• Very inflexible architecture

55. • Limitations in current Icinga interfaces
• Really hard to extend and integrate
• No unified interface so far

56. • Easy to extend and embed
• Multiple authentication providers
• Support for db and livestatus
• Responsive

57. Web 2
Monitoring Docs
BP Graphite PNP

58. Demo

59. THE COMMUNITY

60. You?

63. Icinga Camp - Portland 2015
October 10th
Icinga Camp - Kuala Lumpur 2015
June 9th

64. Training in India
http://olindata.com/training/upcoming

65. CONCLUSION

66. Our vision of integration

67. • Download Icinga 2
• Rethink you configuration
• Install Icinga Web 2 and play with it
• Give us feedback

68. THANK YOU!
www.icinga.org
dev.icinga.org
git.icinga.org
@icinga
/icinga
+icinga