Good day all.

I'm really struggling to get Icinga2 to work correctly for us. I hope that
somebody can point me in the right direction, as I'm sure I just
misunderstand how it's supposed to work.

My set-up for testing is as follows.

* I have one server installed the ppa:formorer/icinga ubuntu repo (version:
r2.3.2-1) using the "master set-up" running "icinga2 node wizard"
* All clients are installed using the same repo using the "satellite
set-up" running "icinga2 node wizard"
* CN and Local Zone is the client hostname.
* Master CN is the master hostname
* I'm using icinga2-web with icinga2-ido-mysql for the dashboard.
* I use "icinga2 node list" on the master to discover the clients and
"icinga2 node update-config" to add them to repository.d

>From what I can see this is how the documentation recommends you set-up
clients with local configuration, sending their inventory to the master.

Here are the questions that is not really clear to me.

* Should all checks be done purely on the client and nothing on the master
?
* If so, how do you deal with checks that you want to run from the master,
like check_http ?
* If you can runs checks from the master related to a client like
check_http, how do you pass the check the correct host address without
having to configure it in hosts.conf on the client ?

this is just a test, but our actual use case is having multiple "masters"
in DMZ locations around the world, receiving checks from machines in the
DMZ and relaying the checks to a master monitoring server which will handle
dependencies and notifications and graphing.

Not really sure if I'm making sense, if so please ask for more information.

Just really trying to wrap my head around getting the most out of Icinga2.

Regards

-- 
-- <X-Clacks-Overhead: GNU Terry Pratchett>
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to