Max wrote: > Thanks Assaf, it looks pretty good. > > Couple of questions to make sure we're thinking about the same scenario :) > > The main problem for me is that currently all the checks for services in > remote DC are running from our central nagios server and there're a lot > of false positives triggered due to latency in communication to that DC. > > As far as I understood to avoid those false positives I should setup > icinga instance in DC, connect it to central monitor via nsca_addon and > set freshness_threshold. > > Is that so? > Have somebody tried to actually implement this in production? > > It is also mentioned in documentation that "services are occassionally > actively checked from the central server" - did I got it right that it > is possible to force ALL the checks for remote DC to be performed by > remote icinga instance only? > > best regards, > Max. > > I have not done it with icinga , but with nagios and the nsca ,I have a central server and several remote servers submitting the results back and it works with no issues.
I don't want to make any promises , but i think it should work with Icinga smoothly too( icinga as the remote or as the master - i do not think it will make a change). Assaf -- Never,Ever Cut A Deal With a Dragon ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
