On 20/08/15 00:23, Josh Cullum wrote:
Hi All,
I'm a new user of Icinga2, we are looking to replace our Nagios
(outdated) monitoring with Icinga.
Currently we have three separate instances of Nagios running
monitoring different areas of our network, and I'm currently trying to
build a master, which has local configuration on it, as well as
connecting it to two 'remote' clients that each manage a HPC Cluster.
The master will only see the results of the checks that are taking
place, and show the host groups that a particular node belongs to, the
checks being defined on the remote client (there are specific checks
that we can and cannot run from certain places within the network). So
the setup is a tiered system whereby the master can talk to anything
through it's gateway that is defined in the local configuration, and
the two clients, which are then connected to their own networks with
the remote hosts attached. The master cannot talk to any of the remote
hosts directly.
I've managed to get the master working with local configurations as
well as two remote clients, and add one node to the remote client,
however, when I run icinga2 node update-config to view the new node on
the master, the master overwrites all the checks defined in the
configuration on the remote client, with it's own ones, which fail
because of the network access rules. (Ping seems to be the default).
I've tried getting it to set other checks, but they just end up with
an unhandled (blue) state.
We're also seeing an issue where if you set the disk to be checked of
the remote machine (not the client) The disk for client is returned in
the result and not the disk for the remote host.
Does anyone know how I can get the clients to set and run all the
checks for their remote hosts, and report back to the master, without
the master overwriting all the checks (to the default PING check), and
the remote hosts being presented in the correct groups in the master,
without having to alter each individual remote host config file?
Any help greatly appreciated.
Kind Regards,
Josh Cullum
Systems Administrator
CFMS Services Ltd
www.cfms.org.uk <http://www.cfms.org.uk>
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
Hello Josh
From first read of your email it seems that a satellite setup will be
more suitable to your requirements and not a master/client configuration.
As far as I understood you had a distributed setup with the old system
and want to replicate this in a similar manner :
https://www.icinga.org/icinga/icinga-2/distributed-monitoring/
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc#!/icinga2/latest/doc/module/icinga2/chapter/icinga2-client#icinga2-client-configuration-local
Assaf
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
