<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 30/03/11 14:00, Gerheim wrote:
<blockquote
cite="mid:AANLkTik9kEQ8Se4VSsJQqzEDqgBu-vRBW21hxOKODiE9@mail.gmail.com"
type="cite">Hello folks,
<div><br>
</div>
<div>I'm new on Nagios and nagios-users mailing list.</div>
<div>I was looking for addons for Nagios but i didn't find one
wich attends me.</div>
<div>Let me explain my scenario. If someone could help me, i ll be
grateful.</div>
<div><br>
</div>
<div>I have one nagios central with centreon. I have another
nagios (worker), with centreon, wich i want to configure some
hots and hostgroups that i don't want to configure on nagios
central. But i want to monitor workers host and hotsgroups with
nagios central.</div>
<div><br>
</div>
<div>Summarizing, when i manipulate hosts on workers i don't want
to put in nagios central.</div>
<div>I've found NCSA, DNX and Gearman but it don't help.</div>
<div><br>
</div>
<div>Could anyone?</div>
<div>Thanks!</div>
<div><br>
</div>
</blockquote>
<br>
At $dayjob I discovered the same problem, however we also had
another problem in that a lot of the servers we want to monitor are
in "walled gardens" and only have http(s) access to the internet.<br>
Our solution was to semi-create our own uploader mechanism, we use
nsca on the receiver side and use a custom submit_check_results that
instead of piping the results through nsca_send it writes them into
a data file for the time/service which gets stored for scheduled
upload via cron.<br>
This scheduled uploader keeps track of the hosts/localhost.cfg file
and if it detects change adds that to be uploaded too. These files
are then bzipped and uploaded via curl to a php script on the nagios
server that knows how to save them in for use.<br>
The nagios server then has a scheduled process that first looks to
see if there's a new config file for hosts and moves it into
etc/hosts/*.cfg ( separate files per host ) and then reloads nagios,
it then takes the contents of the remaining nagios data files and
pipes the contents of them through ncsa. <br>
Although this scenario is far from perfect and we've only been
working on it for 2 weeks on and off it seems to suit our needs.<br>
Maybe looking at a config collector plugin, something like the cisco
router config one, and modifying it to store the nagios host config
could be used to pass the config through nsca, although I'm not sure
how you'd process that on the server to update the host config
there.<br>
<font color="#003300"><i><br>
</i></font>
<div class="moz-signature">-- <br>
<br>
Steve Wilson<br>
</div>
</body>
</html>