2009/4/15 Lance Raymond lraym...@weatherflow.com:
I'm not sure I should say sorry for the basic questions as this is what the
group is for, but seeing some of the in depth questions... talk about an
inferiority complex. Well, I now can see how to debug the start (thanks
Marc) and figured my one problem. But back to a basic few things. I am
looking to have nagios monitor 40 or so servers. 10 or so webservers, a few
database, all have ssh, etc. so as I am trying to lay this out in my head,
for an example, is this the right thinking.
Each box has an unique name in a server folder, /server/servername.cfg
(that is what I have started and kind of working).
The webservers will have the following;
the define host {
host_name
address
use (I think this is my problem)
}
Now the above, the use I think is the actual hostgroup I wish it to belong
to (ex, webserver, linux-server, etc.) I am thinking I will have group
temapltes, webserver will have an http test, linux-server can have an ssh
check, load, users, etc. Now if the above is making sense, the use will have
multiple, ex,
use webserver, linux-server (I assume this is possible) That would
take care of defining the default services to check for those particular
box's.
I guess I am looking for both confirmation and suggestions on some high
level down setups. I don't want each host having 10 define_service items.
I would rather say he is a webserver, and linux box. That by nature will
check x, y and z. The problem so far is I have 4 servers, and even though I
have an address in each, the use is still the default so ALL the box's
details, users, swap usage, etc. is referenceing the localhost and not that
individual box.
That is where I am stuck, the doc's are really not to helpful, but I am
trying to understand more the seperate files. How the use works, when to
use a hostgroup, etc. I will gladly provide cfg files or if someone has
some basic things (aside from the install templates) or some help on the
above it's appreciated.
The main trick to note here is that you can specify hostgroup_name in
your service definitions.
In your linux-server host template for example, you can have:
hostgroups linux-server
How you organise your config files is pretty much up to you. I have a
templates directory containing all my templates, and name the files
for example host-linux-server.cfg, host-wintel-server.cfg,
service-ftp.cfg and so on. I have a directory for each node type
(server-wintel, sever-linux, routers, switches, etc,.) in each of
these I have files for both host and service definitions. Some
services are not specific to any one host type, so I have a seperate
services folder for these generic service definitions (things like
ftp, http, telnet go here). This works for me, but might not go with
the way you think about your systems.
I heartily recommend you buy the book Nagios by Wolfgang Barth as it
gives an excellent head-start in understanding many of these issues.
http://nostarch.com/nagios_2e.htm
hth,
Jim
--
Web Admin for Corsham Diary http://corshamdiary.org.uk
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
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
