This document discusses monitoring an OpenNebula environment with Icinga. It introduces Icinga as an open source enterprise monitoring system that checks resource availability, notifies users of outages, and provides business intelligence data. It describes Icinga2's architecture as multithreaded and automatically load balanced. It then discusses how to specifically monitor OpenNebula, including checking the availability of physical infrastructure, OpenNebula services, and interfaces/APIs, as well as monitoring capacity and providing business/customer views of monitoring data. Configuration examples are provided to define services and apply checks using Icinga2.

1. www.icinga.org
How to Monitor your OpenNebula
Environment with Icinga
Barcelona – 10/20/2015

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

3. ICINGA - INTRODUCTION

4. Quick Poll

5. 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.

6. • Originally forked from Nagios in 2009
• Independent version Icinga 2 since 2014

7. • Monitors everything
• Gathering status
• Collect performance data

8. • Notifies using any channel
• Considers dependencies
• Handles events

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

10. ICINGA2 - ARCHITECTURE

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

12. Checker
Notify
Gelf
Perfdata Graphite
IDO
Compat
Livestatus

13. Our vision of integration

14. MONITORING OPENNEBULA

15. • Availability monitoring
• Capacity monitoring
• Business / Customer view

16. • Availability
• Physical infrastructur
• OpenNebula services
• Interfaces and APIs

17. Physical infrastructure
OpenNebula services
User interfaces

18. • Monitor using standard checks
• Gather as much information as possible
• Take care of the metrics
• Use a scalable configuration

19. define service {
host_name one1, one2, one2 … , oneX
service_description one-service
}

20. apply Service ”one-compute" {
import ”one-node”
check_command = ”one-service”
assign where host.address
&& host.vars.type == ”ONE-KVM”
}

21. • Capacity
• Physical capacity development
• Service performance and trends

23. # icinga2 feature enable graphite

26. • Business view
• Hide the technical details
• Differentiate outtage types
• Provide a top-down view

28. CONCLUSION

29. • Split your setup into perspectives
• Monitor individual components
• Check the service availability
• Create a business process
• Of course use Icinga2

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