Hi there, we played around with the new agent integrated in icinga2 since version 2.2
The new agent+api have two remote-check-soulutions:
- 1) remote satellite checking
- 2) remote command execution on client (similar to NRPE)
There is a great difference between both options. For the first it is
possible to create automatically the configuration-file from the client
on the master (API+Repository).
To keep the effort of the client-system administrators low, I think the
second option (remote command execution) is more attractive. But there
is no way to generate automatically config-files (like check_mk).
It would be cool if nrpe and ckeck_mk could be replaced by i2-agent+API.
So our thoughts:
For remote checks i2 Master and Client are configured as "remote command
execution" [1].
On the client icinga2 the administrator creates a config like
remote.commands.cfg. In this config-file you can easy migrate the
nrpe.cfg to the new icinga2 (remote client).
e.g.:
nrpe.cfg:
command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
30,25,20
remote.commands.cfg:
object CheckCommand "check_load" {
import "plugin-check-command"
command = [ PluginDir + "/check_load" ]
arguments = {
"-w" = "15,10,5"
"-c" = "30,25,20"
}
}
Well, now the i2 master can ask the client over the api about his state.
Now it would be awesome when the i2 master can ask the api of the client
which checks are listet in the remote.commands.cfg (or $.cfg) and
creates automatically the config-file. Is such a feature planned?
What do you think about that feature?
Another problem for remote command execution is that both strings of
"CheckCommands" musst be identical on i2-master and i2-client. But when
the service-check-command on the client side called "check_load" and the
remote-check-command on i2 master called also "check_load" but
"check_load" is not defined (in the commands.cfg or ITL) on i2 master
the i2 master instance didn't start. But it is not important for the
master that these command is (or is not) defined. So a flag would be
helpful which excludes the is-the-check-command-defined option.
In my opinion both options (combined with monitoring-plugins) close the
gap between icinga2 agent+api and nrpe+check_mk.
What do you think about that?
Are such features already planned or integrated?
Thanks for the great work on icinga2!
Greetings from Ilmenau
nuts
[1]
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/monitoring-remote-systems#icinga2-remote-monitoring-client-command-execution
signature.asc
Description: OpenPGP digital signature
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
