On 22 May 2010, at 15:46, Toni Van Remortel wrote:
On 20 May 2010, at 14:19, Toni Van Remortel wrote:
I had a quick look at the contacts.cfg file, and it shows me a
possible source of the problem: large amount of host groups (163)
and service groups (143) associated with various contacts.
I have many groups that are eg about Servers, but for every site I
create a separate group. So I have 9 hostgroups for Servers, 9 for
Switches, etc.
Stepping back a bit, why are there so many host groups and service
groups?
Well, I have different sites, but they have local administrators. So
I need to have a good separation in the hosts and services for every
site. That’s why I have so many groups.
Every site thus has a full hierarchy tree, but this means I have to
maintain several of these trees here on the top.
A nice feature would be to have another property on each host: site
or company. And the option to link this to a user. Would make it
much easier for me J
What would "site" property look like? Does site == slave?
Currently, role selection is via host group in hierarchy UNION slave
selection. Would UNION keyword selection help (could then have a
keyword = services on a site)?
Does this take > 6 minutes?
Nope:
nag...@node5:~$ time /usr/local/nagios/bin/rc.opsview check
Checking configuration for /usr/local/nagios/etc/nagios.cfg... okay
real 2m16.410s
user 2m11.240s
sys 0m1.090s
Just to let you know that I've reproduced the problem and Nagios
stalls in the conf.d directory. Must be a bug somewhere in Nagios for
reading subdirectories. Haven't had a chance to look at this yet, but
will try and get this into 3.7.1.
Ton
_______________________________________________
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users
