On Wed, Dec 29, 2010 at 10:52:45PM +0000, Jim Avery wrote: > On 29 December 2010 18:36, stan <[email protected]> wrote: > > I am trying to rationalize a couple of Nagios configurations that have > > 2different histories, and they seem more different than I think they should > > be. So, first I want to get the big picture n my head, and decide what > > seems to be a sensible configuration to support going forward. > > > > Basicly I have in mind some thing like this. > > > > 1. Define hosts in a file > > 2. Define services in a file > > 3, Define commands in a file > > 4. Aggregate hosts in groups of similar types in a hostgroups file > > 5. Aggregate services in groups of similar types in a servicegroups file > > > > > > Now, where I start to get confused here is that the service definitions > > seem to have a filed for one or more hostnames. Why is this? > > Services are often quite agnostic as to what kind of host they relate > to. Take for example FTP. Various host types will accept an FTP > connection but the service definition for them will always be pretty > much the same. >
Thanks for the thoguhtful reply. I am still confused by why the service def's have a filed for hostname. As you point out, services don't necisarily relate to hosts. They are functions provided, or statuses of a machine. and I would think thta servicegroups would be where the assoctation betwen the service, and thehosts that you want to check for that service wouldbe. Am I missing something? ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Nagios-users mailing list [email protected] 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
