Sorry for the top-posting: I'm stuck with Outlook. Have you tried templates? We have ~550 hosts and ~4500 services, and it'd be a real pain to not use templates.
I have a host template definition for Windows servers, which adds anything assigned that template to a windows_servers host group. I have a bunch of services defined which are assigned to everything in the windows_servers host group. When I add a new Windows host, I put "use prod_windows_server" in the host definition, and the host is automatically assigned service checks for CPU, C drive, E drive, memory, page file, running antivirus, and a couple others. I have a similar setup for development servers, but we don't let them send notifications outside of work hours. For servers needing extra checks, I just add the extra service checks to the hosts that need them. For the servers which aren't standard for our environment (some predate the standardization push and have a D: instead of an E: drive, for example), I put a !hostname in the appropriate service check definition. -----Original Message----- From: Keith Edmunds [mailto:k...@midnighthax.com] Sent: Monday, February 02, 2009 11:19 AM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Disable inherited checks? > You can disable inherited service checks for a host by putting an > exclamation mark in front of the host name in the service definition. > Look for "Excluding Hosts" in > http://nagios.sourceforge.net/docs/3_0/objecttricks.html. Thanks Chris. The problem with that is that I need to list all hosts in the service definition. The problem I'm trying to solve is that we monitor around 70 nodes with Nagios, and when we add a new monitor, we have to update all host files and it's easy for some services to be missed on some nodes. To avoid that, I'd rather set things up so that all hosts monitor all services except where specifically excluded. In other words, everything on by default and selectively turn off what is not needed; it seems that Nagios works by having everything off by default and selectively turning things on. I can, of course, put "host_name *" in the service definition, but then I need to disable that service for some hosts. Hmm, thinking aloud, maybe I can do "host_name *, !not_this_one, !or_this_one ... I'll try that. Thanks, Keith ------------------------------------------------------------------------ ------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Nagios-users mailing list Nagios-users@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 Nothing in this message is intended to make or accept and offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Nagios-users mailing list Nagios-users@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