#34 Realms / Groups of worker nodes

[Anonymous]

I'd like to see a way to group the worker nodes in either realms or some other way in the configuration on the master server, or a parameter in the config in the worker.
The reason behind this is because in larger environments, just like what DNX is designed for where there are many monitoring servers, there are different company policies of what can access what.

DNX is designed in such a way that only the worker asks for the jobs todo, not the server, which is the first step towards this feature in terms of how work can traverse the zones.
The second step is a similar that is already being done in the checks specified ONLY for the local server with regexp.
I'd like to have a way to make different groups/reams, based on the similar function to route specific checks to localhost.

As a configuration, it could be similar to how the configuration in Nagios is built up today, with a simple define:
define group/realm{
name
alias
members
regexp
allowoutsidework
}
The name / alias is for logfiles.
Members can be the IP's of the workers asking.
Regexp is the same as localCheckPattern
AllowOutsideWork is meant as a last option, if no members ask for work, let it delegate to someone outside the group/realm. In most networks, this would mean the check would fail because its not allowed, but it can be in environments its policy to have primary and secondary servers for work, ex: physical workers, vm workers as backup.

[HaDeS]

I too would like to see this implemented. Good thinking on the 'AllowOutsideWork' option as the work should fallback to other DNX client(s) if the preferred DNX client(s) happen to be down. I am requesting this for a different reason, not for security but for location. I would like to use preferred DNX clients based on physical location and keep the nagios checks local.