Nagios

Phil Regnauld (regnauld) writes:
> 
> host "myhost" {
>     host_name "myhost";
>     addresses  { default 192.168.1.1; 123.45.67.89; };
>     service { dns; http; ping; }
>     service { dns_in "DNS_IN" { 123.45.67.89; }
>                                               
> }
> 
> It's IMHO easier to configure and parse, maybe it's just me :)
            ^^^^^^^^^^^^^^^^^^
	Ahem, I even forgot two semicolons in the above block -- this is
	left as an exercise to the reader 8-)

Hey Phil,

On Sat, 2002-04-06 at 21:21, Phil Regnauld wrote:
> Phil Regnauld (regnauld) writes:
> > 
> > host "myhost" {
> >     host_name "myhost";
> >     addresses  { default 192.168.1.1; 123.45.67.89; };
> >     service { dns; http; ping; }
> >     service { dns_in "DNS_IN" { 123.45.67.89; }
> >                                               
> > }
> > 
> > It's IMHO easier to configure and parse, maybe it's just me :)
>             ^^^^^^^^^^^^^^^^^^
> 	Ahem, I even forgot two semicolons in the above block -- this is
> 	left as an exercise to the reader 8-)

Haha ;)

No, seriously. I think this is a bad idea with the current way
configuring Nagios. I mean: try to parse it.. even as a human ;)

I just wonder why Nagios developers didn't go for the XML style..

It would nevertheless be nice to have more ips per host.. But if a
service runs on all (most -badly- configured onces do), it's enough to
check only one.

Geert

-- 
Geert Vanderkelen
Kemuri.Org

http://kemuri.org

Geert Vanderkelen (geert) writes:
> Hey all,
> 
> I was wondering what Nagios users use for the extra link to Extended
> Host information.

	I use a cgi handler which is passed the hostname.

> For instance, it would be nice to attach a possible or the solution to a
> critical problem for a certain service through this. Like this dream
> option for hosts/services:
> 
> 	what-todo-critical https://nagios.foobar.info/warning?$HOST$

	Or better:

	notes_url	/cgi-bin/url-handler.cgi?$HOST$&$ALERT$

	Where ALERT is ok, warning, critical.

On Saturday, April 6, 2002, at 05:57 AM, Geert Vanderkelen wrote:

> Hey all,
>
> I was wondering what Nagios users use for the extra link to Extended
> Host information.
>

I actually don't use the link for linking to information pages. I use it 
to link to the actually host/service that is being monitored so you have 
one click verification that the service or host really is down. For 
example, for services links I link to the url that is being monitored 
to. You click the link and your browser will try to open the page that 
is being checked. If it doesn't come up, you know for sure that netsaint 
is correctly reporting a service failure. My netsaint installation is 
actually on a completely separate network from all of our other systems. 
Having multiple admins in different locations double checking a service 
helps us know for sure that a service really is down, or if it is only 
down from netsaint's perspective. For hosts I generally put a link to 
the java vnc server for the host, so you also have one click access to 
login to system and try and troubleshoot it (i.e. restart iis/coldfusion 
etc etc). Works out pretty well.

--Paul Baker

Hey Paul,

Doing it your your way seems to limit the infit use of that External
Link. :)
Now, ok, if it works out.. But what do you do with DNS, SSH, MySQL.. Or
are you only using it for HTTP? In your situation putting the plugins in
into a cgi-bin and accessing them somehow would be reasanble :)

Actually a check without delay, immitiadally would indeed be nice.


Geert

PS: I was troubled about why using VNC to 'troubleshoot' a system. Then
I saw iis and remembered euh.. jah.. windows ;) No offense huh. hehe :)

On Sun, 2002-04-07 at 00:20, Paul Baker wrote:
> > I was wondering what Nagios users use for the extra link to Extended
> > Host information.
> >
> 
> I actually don't use the link for linking to information pages. I use it 
> to link to the actually host/service that is being monitored so you have 
> one click verification that the service or host really is down. For 
> example, for services links I link to the url that is being monitored 
> to. You click the link and your browser will try to open the page that 
> is being checked. If it doesn't come up, you know for sure that netsaint 
> is correctly reporting a service failure. My netsaint installation is 
> actually on a completely separate network from all of our other systems. 
> Having multiple admins in different locations double checking a service 
> helps us know for sure that a service really is down, or if it is only 
> down from netsaint's perspective. For hosts I generally put a link to 
> the java vnc server for the host, so you also have one click access to 
> login to system and try and troubleshoot it (i.e. restart iis/coldfusion 
> etc etc). Works out pretty well.
> 
> --Paul Baker
> 
-- 
Geert Vanderkelen
Kemuri.Org

http://kemuri.org

Hey,

Erm, I think that I speak for everyone by saying that your first problem
is just a matter of reading the documentation. You have to setup the
Apache authentication and enable it in the cgi.cfg. There are people
putting time in writing docs you know :)

Also, if you start using it, try Nagios. It has better configuration
possibilities. Nagios is the renamed Netsaint and offers more.

There are examples included with the source code.

And if in the end it doesn't work out.. Come back to the list. ;)

Geert

On Sat, 2002-04-06 at 13:09, saravanakumars wrote:
> Dear friends,
> 
> 
> 1) I installed the Netsaint-0.0.7 in Redhat Linux7.1.
> 
> 
> i installed the neatv4.9 and also the plugins.
> 
> 
> Now the netsaint is running and also i am getting it in browser. I mean the first (main)page and document pages (cgi) are opening. But not the others, like status map, 3D status, summary, service information, host information ec.,
> 
> 
> And also not the configuration screen.
> 
> 
> What i have to do for viewing all screens (CGIs)?
> 
> 
> 2) I am using one linux m/c (gateway), 2 NT servers, & 10 NT wirkstations.
> 
> 
> how to make entry of these systems in the configuration file, so that to monitor these systems. I am using the private static IP address (192.168.50.0) for LAN.
> 
> 
> Can anybody send a typical model file for me.
> 
> 
> Thanks a loy !
> 
> 
> saravanans

-- 
Geert Vanderkelen
Kemuri.Org

http://kemuri.org