cross products: host/host group x service/service group ..?

Jan Grant jan.grant at bristol.ac.uk
Thu Jan 24 11:23:46 CET 2008


By-and-large, I generate my nagios configs mechanically from the same 
config that drives app deployment. However, I've just had cause to write 
some config by hand and the following occurred to me:

I've got several hostgroups, and several service groups. What I'd really 
find convenient is a way to say

	all these services are running on all these hosts

and generate service instances for the product of those two sets. (The 
hosts are part of a farm.)

It's obviously possible to get a lot of the way using service templates, 
but as far as I can tell I still have to write a service definition per 
(host, service template) pair.

I'm aware that there may be design issues I've missed - naming 
considerations or suchlike. I think it'd be desirable to be able to 
specify groups of hosts and groups of service templates and (with a 
small number of additional declarations) create service instances. So 
(a) am I just being dumb and missing an already-extant capability; (b) 
is there a fundamental reason why this doesn't fit in nagios' design; 
(c) is the typical thing in this situation to do what I already do and 
generate the configs mechanically?

Cheers,
jan

-- 
jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
Tel +44 (0)117 3317661   http://ioctl.org/jan/
Ever see something and think, "I've gotta leverage me some of that?"
Odds are, you were looking at a synergy and didn't even know it.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list