Hi all,
I finished the nrpe module for the pollers. Now you don't have to launch the
check_nrpe binary to talk to a nrpe server. This module should be seen as a
performance booster : less fork, less CPU usage (and especially in kernel
mode, so virtual machines will be happy...).
How does it work? It's very simple in fact :
* you define a module for your poller :
define module{
module_name NrpeBooster
module_type nrpe_poller
}
And link it to your poller object :
define poller {
[....]
modules NrpeBooster
}
the poller will launch specific workers for this module.
Then you need to "tag" your commands for using this module. The easier way
is to use :
define command{
command_name check_nrpe
command_line _nrpe_poller -H $HOSTADRESS$ -u -t 9 -c $ARG1$
-a $ARG2$ $ARG3$
}
The arbiter will see the _ before nrpe_poller, and apply automatically a
module tag "nrpe_poller" to it.
Another way is to explicitly add the "module_type" parameter to the command.
This module will simply parse the command_line and open connexion to the
nrpe server. The SSL connexion is managed, and all connexions are managed in
a asynchronous way of course :)
I'm wondering if we should change the nrpe_poller to simple nrpe because
such module can be useful for reactionner too after all.
Feel free to test it, and why not bench it :)
Jean
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
