Did you know that you can navigate the posts by swiping left and right?
Part 01 — Setting up our Icinga2 Lab
Part 02 — Installing Icinga2
Part 03 — Installing IcingaWeb2
Part 04 — Establishing the Master Satellite Relationship
Part 05 — Addressing Design Flaws
Part 06 — Installing Icinga2 Director
Part 07 — Adding Client Endpoints
Part 23 — Summary
I was recently tasked with building out distributed monitoring for our infrastructure that spanned two physical sites and AWS. We decided to go with Icinga2 since that seemed to be the agreed upon best choice. The documentation felt more like a reminder or reference guide for those that have already had experience with Icinga2. Hopefully this guide will help others like me who are brand new to Icinga2 and need help getting started. In this first part we will setup our simulated multi-site environment. I am doing all of this off of my home lab R720 server. I gave each host, except the master, 50gb of storage, 2gb of RAM, and 2 CPUs. I gave the master 8gb of RAM and 4 CPUs since it has to handle a backend database. We will be placing the master in Site-B to simulate it being in AWS. Since the master server does not do any checks itself, we will also need a satellite in Site-B to monitor our host.
During this journey I will working towards getting distributed monitoring. Specifically, I will be trying to setup what the documentation calls Top Down Command Endpoint. I will have one master server that will be run the web frontend and three satellites, one for each site, that the master will communicate with. I want the satellites to run remote HTTP, WinRM, SSH, and ping checks on the hosts that are in their respective zones and then report back to the master which will display the results on the frontend.
Don’t worry if these terms do not make sense right away. I will add context to them as we go through this journey.
Its important to draw out your environment and plan out how you want to setup your master and satellites. I will be using my home lab to simulate a multi-site setup by using VLANs and firewall rules.
iptables -A INPUT -s IP-ADDRESS -j DROP
ESXI 6.7 Hypervisor
Roland Sommer and William van Beek on the Icinga community forms as they provided the critical information I needed to succeeded.