Hi all,
It seems that the distributed passive checks was need ;)
So I just pushed the shinken-receiver code in the git repository :)
The definition is like all others :
define receiver{
receiver_name receiver-1
address localhost
port 7773
#modules NSCA
timeout 3 ; 'ping' timeout
data_timeout 120 ; 'data send' timeout
max_check_attempts 3 ; if at least max_check_attempts ping
failed, the node is DEAD
#advanced
realm All
}
This daemon is totally optional of course.
It's main goal is to get all passive "things" (checks but why not other
commands) in distant realms. You can see it as an "passive buffer" that will
be reap by the arbiter so this one will dispatch commands like if it was it
that get the commands.
"spare" is not important for this daemon, because it not responsible for any
configurations, and will not open connexions to any other daemons.
Of course without module this daemon is useless. It can use the arbiter
ones, so from now mainly NSCA from now, but other will be added I think.
the realm is not so useful to, it can get data from what you want, not only
from its realm.
>From now there is no init.d script to launch it, but it will came, like for
the documentation too :)
Feel free to test it, it's launched like all other daemons :
bin/shinken-receiver -c etc/receiverd.ini
So now even the passive checks are easily scalable :)
Jean
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
