passive host - distributed monitoring

[Marco Supino]

Hi,

If I disable active checks for services, if a service has a problem, it will show up in the TAC as "Disabled" instead of "problem", 

I want errors to show up as problems, colored in red, and playing the WAV associated with the problem's level , If its disabled, its not "highlighted",

I followed this http://nagios.org/faqs/viewfaq.php?faq_id=271 in order to achive the status of "passive - and not disabled - and freshness checking",

The way I wanted it to work is that active checks are regularly scheduled, but if the results are below the freshness threshold, the service check should not run, and be rescheduled, it does not work in this way.

Marco.
 

-----Original Message-----
From: nagios-devel-bounces at lists.sourceforge.net [mailto:nagios-devel-bounces at lists.sourceforge.net] On Behalf Of Hendrik Bäcker
Sent: Saturday, April 14, 2007 17:07
To: Nagios Developers List
Subject: Re: [Nagios-devel] passive host - distributed monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Marco Supino schrieb:
>
> Hi,
>
> My current scenario is that the central server can not reach the
> hosts that the distributed server is checking.
>
> I tried using the method from the doc when I set the system up, but
> what I saw is that even if a service is "fresh", an active check is
> still made according to its schedule, and then it becomes unknown -
> stale,
>
> Marco.
That's ok.

If your master cannot reach the others, you have to ensure that he
doesn't try it.

So disable active checks for those and define a stale command that
goes into a state you want if nagios reaches the freshness threshold.

Once again - where's the problem?

As long as your central nagios is getting passive check results the
freshness will be under the threshold and you see the results as they
are on your distributed systems.
If something went wrong while transfer the check results between
distributed server and main server, the freshness screw up to your
configured threshold, nagios executes the check_command for this
host/service which will only say for example "CRITICAL - SERVICE STALE".
At this level you know that there's something wrong between your
nagios servers / nsca communicaton or similar.

Kind regards,
Hendrik


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
 
iD8DBQFGIOAXlI0PwfxLQjkRAtxXAJ0Tslu+XNomOkt/HQwIj+GefsFNuwCfUece
7620QPr+njrkSWqBlJoQd+k=
=utP0
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/