<div>I should have been more precise regarding the cluttering of the display - it was the hostgroup display I was referring to. :/</div> <div> </div> <div>Would it be an idea to as much as possible use this configuration method: hosts --- hostgroups --- services? To elaborate some: Hosts are always connected to host groups, and the same for services. This way one will avoid linking services to specific hosts, making the service definitions more clean. </div> <div> </div> <div>Also, I'm thinking about having a host group called for example "linux-servers", to which all linux servers are linked. A number of service checks common for all linux servers are also linked to this host group. When adding new linux boxes I simply link them to the "linux-servers" host group, and add extra services checks where needed. In a similar fashin I would create a host-group called for example "dell-servers" to which all Dell hosts and related service checks are linked. New Dell servers are then linked to this host group.</div> <div> </div> <div>I'm thinking this may be a good idea, but would like to hear how others have structured their configuration and if there may be some hidden pitfalls in my proposed configuration method. </div> <div> </div> <div>On 9/16/08, dave stern - e-mail.pluribus.unum <<a href="mailto:dit.dash@gmail.com">dit.dash@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Not quite sure what you're trying to do. If you monitor a service, it's going to be on the nagios service details pagre regardless, That's the whole point. There are some tricks to slim down some other displays eg I define a whole bunch of services under a host without defining the hosts these services run on explicitly. I just feed the IP address as part of the check_command. This reduced the hostgroup grid page. I don't think that will work for you. If you're asking how to most efficiently code this in your configs, the timesaving tips page mentions ganging together services. ie you don't need a service stanza for each host you want to run this on. Rather, use a wildcard or group. define service{ use generic host_name hosta, hostb hostgroup special-ones,!webguy ..... } Run the service on hosts hosta, hostb, all hosts in the hostgroup, "special-ones" but not "webguy" One other thing you should consider. Where will the plugins live? The easy answer is to put them on an NFSmounted partition that all hosts can access and that you can easily update. This is a bad practise. What happens when NFS breaks? You should really copy the plugins to each host st they run locally. On Tue, Sep 16, 2008 at 8:05 AM, Kenneth Holter <<a href="mailto:kenneho.ndu@gmail.com">kenneho.ndu@gmail.com</a>> wrote: > > Thanks for the reply. I'll read the documents you listed. > > Meanwhile, I have a design question: What's the best way to set up a service > check to be executed on a selected few (or maybe all for that matter) nodes? > Say I need to monitor a particular process (lets call this service A) on a > number of systems, how would I implement this? I guess one way would be to > link service A to a hostgroup, say hostgroup A, and add the selected systems > to that hostgroup. This, however, will somewhat clutter up the web display, > so I'm looking for alternative approaches. > > Any suggestions? > > > > On 9/15/08, dave stern - e-mail.pluribus.unum <<a href="mailto:dit.dash@gmail.com">dit.dash@gmail.com</a>> wrote: >> >> Assuming you're already familiar with nagios, I'd look at the nagios >> documentation >> in the following order: >> >> Under "Configuring nagios", look at "Object definitions" and make sure >> you understand all parameters and what would make sense in your >> environment >> Under "Advanced Topics", look at "Timesaving tips for object definitions" >> Under "Advanced Topics", look at "host and service dependancies" >> >> Under "Advanced Topics", look at both "Distributed Monitoring" and >> "Redundant and >> Failover Monitoring". >> Finally, under Security and Performance Tuning, look at Large >> Installation Tweaks >> >> On Mon, Sep 15, 2008 at 10:23 AM, Kenneth Holter <<a href="mailto:kenneho.ndu@gmail.com">kenneho.ndu@gmail.com</a>> >> wrote: >> > Hello all, >> > >> > >> > I'm new to Nagios, and are planning on using Nagios for monitoring our >> > network of Linux servers. >> > >> > Are there any best practice documents on how to manage the different >> > definitions such as hostgroups, services, servicegroups, and so forth in >> > an >> > enterprise environment? >> > >> > >> > Regards, >> > Kenneth Holter >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> > challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> > world >> > <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a> >> > _______________________________________________ >> > Nagios-users mailing list >> > <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> >> > <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> >> > ::: Please include Nagios version, plugin version (-v) and OS when >> > reporting >> > any issue. >> > ::: Messages without supporting info will risk being sent to /dev/null >> > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a> > _______________________________________________ > Nagios-users mailing list > <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> > <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > </blockquote></div>