From: SourceForge.net <no...@so...> - 2007-03-01 14:57:29
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4185908 By: rob_blake All, Carrying on from the above work that I've been doing, I've been considering how we should allow the user to define a dynamic remote host. As mentioned above I believe that the user should be forced into providing a set of templates. A template essentially defines a type of dynamic remote host that can join the Blue monitoring network. By defining this template, the user essentially tells Blue that when it sees a host of type 'x' request the join the network, it should apply the templated monitoring configuration. Obviously one of the aims is to keep the definition of any objects as closely tied to the current format as possible. So I am proposing the following syntax for the definition of dynamic templates: define dynamic_template{ remote_template_name db_server uses_host name_of_defined_host_template_in_my_hosts.cfg runs_services comma_seperated_list_of_services_from_services.cfg contact_name contact_from_contacts.cfg contact_group contact_group_from_contactgroups.cfg joins_hostgroup hostgroup_from_hostsgroups.cfg } So in essence I see a host of type 'db_server' attempt to join the network. The dynamic registrar knows what host configuration to apply, what service configuration to apply etc. It then writes this configuration into the dynamic.cfg and issues the command into the external command file for blue to read in the configuration. Obviously the hostname and host address fields of the host definition are changed by the dynamic registrar to that of the host attempting to register. Any thoughts? Rob ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=545812 |