Questions on migrating to DistributedEnvironment on Nag 1.1

[Hochberg, Keith]

James,

No problem... 

The statement regarding host checks is at the end of
http://nagios.sourceforge.net/docs/1_0/distributed.html

"Performing Host Checks - At this point you know how to obtain service
check results passivly from distributed servers. This means that the
central server is not actively checking services on its own. But what
about host checks? You still need to do them, so how?  Since host checks
usually compromise a small part of monitoring activity (they aren't done
unless absolutely necessary), I'd recommend that you perform host checks
actively from the central server. That means that you define host checks
on the central server the same way that you do on the distributed
servers (and the same way you would in a normal, non-distributed setup).
There are ways to obtain host checks passively, but implementing them is
beyond the scope of what I care to write about at this time. :-)"

As for the config files my sympathies for being in a primarily windows
shop :)  I hear NagMin works quite well but I'm not sure if anyone has
used it in a distributed monitoring environment or if it can be
customized to be used in one.  Perhaps someone else has done this?

Regards,

Keith

-----Original Message-----
From: James Harrison [mailto:james.harrison at amcg.com] 
Sent: Monday, October 13, 2003 3:04 PM
To: Hochberg, Keith
Cc: nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] Questions on migrating to
DistributedEnvironment on Nag 1.1


On Mon, 2003-10-13 at 11:37, Hochberg, Keith wrote:
> > 1.  Where do I do check_host_alive? Central or Distributed?
> 
> The central server executes the host check command defined in
hosts.cfg
> after it receives data passively that a service has gone into a HARD
> state.  Passive host checks should be possible with Nagios 2.0 (per
> Ethan).

Thanks, that explains a lot.  Is this info in the doc's somewhere that I
missed?  Should it be added?(I know with 2.0 on the way it may be moot)


> 
> For 2 and 3 I have never seen this happen on my build... the only
thing
> I can think of is to make sure your freshness_threshold is set to an
> interval that the active server should be sending data for that
service.

Ahh!! Freshness threshold indeed.  I loosened it up a bit and all is
better.

> 
> > 4.  For members of the list who are managing large Nagios
> implementations "thousands of services on hundreds of hosts", how are
> your configs managed?  I'm currently using Nagmin, which seems ok, but
> was just curious what big sites might be doing.
> 
> I manage my configs by hand... if you ask me it's the only way to do
it.

I'm in a primarily MS shop and our managers want to make sure that any
of the Linux stuff is "easy" to use/manage if any of us *nix guys
disappear, get runover, etc,etc.  (I'm not sure what could be easier to
manage than a text file either.)  Anyway, I'm tryin' to provide some
kinda GUI so these guys can manage it as well.

Thanks for the info.

-- 
James Harrison RHCE, CCNA


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Nagios-users mailing list
Nagios-users at 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