1
edit
Changes
→Approach
No preliminary preparations needed to occur on the system that Icinga was going to be installed on, the only thing was to install the required packages in order to install the software. These lists of packages can also be found in the Icinga Documentation. While using my four other Virtual Machines as the clients, I was able to test my Icinga configuration, in order for this to be successful each one of the client machines that are running Linux needed to contain the "Nagios Remote Plugin Executor (NRPE)" software and plugin. This allows the Icinga server to execute commands on these remote server to check the CPU performance, users logged in, total processes running, HTTP service, FTP service, etc...
My final approach in the Installation of Icinga was to ensure the configuration files were organized and easy to read. I had created four separate files, each one of them serving their own purpose, one would include a template that would be used for each host system that is to be monitored, the second would contain a list of services that will be checked on each remote system, a hostgroup file that contained a list of ALL of the hosts and mapping them to one single name, and lastly a single host file which would contain all of the hosts that Icinga will monitor. Examples and details of these files I created can be found on my blog as well.
<!-- Describe the approach to the project -- method/procedure/tools etc -->
= Challenges =
To be honest, there are no challenges that I can recall throughout my process. However, listed below is a very small list of what I had encountered that had taken me longer to complete;
* Understanding the configuration files of Icinga and how it will communicate with each host it will be monitoring. Getting a feel of the host configuration files was a little difficult at first. Continuing to work with them made it easier to understand them.
* Working with Mike Kirton in order to build an RPM Package for Icinga became one of the biggest challenges, ensuring that everything would be installed to the proper directories along with the proper permissions that were required for Icinga.
* While having SELinux set to Enforced on my test environment I was running into issues with SELinux preventing some commands being executed, while working with someone in the #selinux channel on irc.freenode.com I was able to create a Icinga SELinux policy, it worked perfectly on my environment.
<!-- Challenges that had to be met to complete the project -->