hostgroup-defined services with notifications defined by other hostgroups?

[Phil! Gold]

I'm sure this is something other people have wanted to do, but I must not
be hitting the right combination of search terms when looking for it.

I have a bunch of servers for which I'm using hostgroups to manage their
monitored services.  In other words, there's a set of standard service
checks for Windows servers, another set of standard checks for Linux
servers, and so on.  I then have subgroups for the hosts at each site:
Windows servers at site 1, Windows servers at site 2, and so on.  I'd like
to be able to use the site groups to determine who gets notifications for
service failures while only defining the services once.  Is this possible?

I suppose I could make something work by hacking with user macros and some
custom notification commands that make their own decisions about whether
to send the emails (or whatever), but I'd rather work within Nagios'
structure.  Is my only option to define a separate set of services for
each site's hostgroups?

-- 
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2  print: D200 5BDB FC4B B24A 9248  9F7A 4322 2D22 026A 27F2
--- --
"I was talking aloud to myself.  A habit of the old: they choose the
wisest person present to speak to; the long explanations needed by the
young are wearying."
                       -- _The Lord of the Rings_, J. R. R. Tolkien
---- --- --

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
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