Hi all, I am currently exploring the possibilities for passive check submission to Shinken. As I understand it, the Nagios NSCA server has been implemented as an arbiter module and listens for messages sent by client_nsca ( or possibly some other program that implements the desired encryption and packet protocol). Unfortunately, this architecture is not distributed, since all checks done on remote hosts must be sent to a single Arbiter instance. Moreover, I don't quite understand why Arbiter was designated for processing the passive checks, even when using only the named pipe, since its main job is supposed to be to distribute the configuration to all other daemons. Wouldn't it be more prudent to have this processing done by satellites, like pollers or brokers? It seems to me that this centralization contradicts the whole distributed philosophy of Shinken, so I wanted to ask on the mailing list if there are any ideas to change this in the future, or even better, if it is possible to have distributed passive service checks in some form with the current version of Shinken?
Greetings, Venelin Petkov ------------------------------------------------------------------------------ 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
