Nagios is badly documented :(

Michael Natale michael.natale at incipient.com
Tue Oct 15 19:36:38 CEST 2002


I should preface my comments by saying that I am new to the Linux O/S and most of my 7+ years of expertise with computers/servers/networking is in the mickeysoft/cisco world.

Having said that, I found the documentation to be very detailed -- more detailed than many programs I have tried to configure/install on Linux.  

For me, lack of detailed documentation aimed at the new Linux user is the primary reason why I stop attempting to configure an app or server running on Linux most of the time.  For some projects, I just don't have time go look up the dozens of terms or acronyms I am unfamiliar with, so I find a different solution using familiar technology and solve my immediate problem.  

Moreover, (ducking here) some Linux user groups, lists, forums, software developers, whatever...seem to have a "well if you don't know you're just stupid and Im not going to waste MY precious time telling you anything bla bla bla" attitude.  Fortunately no one connected with the Nagios project has had that attitude.

With Nagios, I read the entire doc, and had it up and running, monitoring my infrastructure (including notifications) in a day or two of on/off work.  There's still some kinks in my config, but I can iron those out over time.  The app functions as it should with minimal effort on my part.

Unfortunately for the Linux community as a whole, more widespread adoption of Linux as a viable O/S for the desktop or server farm is held up by "Mickeysoft-centric-IT" folks like me, who in reality, don't want to admit to ANYONE that they don't understand something about computers.  We are used to being the answer guy/girls, so we stick with what they know and can solve our problems RIGHT NOW.  BUT, we all know that B. Gates' Evil Empire makes software that is both ridiculously expensive and RIDDLED with bugs, so I don't think there's an IT professional out there who wouldn't switch away from it in the corporate workplace if there were more of a clear path from here to there.  Especially for those of us who have just dabbled with Linux "on the side".

Detailed documentation aimed at the non-linux-pro would solve that....

But I digress....

Thanks for a great app so far,
-Michael 


**********************************
Message: 1
Date: Tue, 15 Oct 2002 12:46:27 -0400
From: "David Rippel" <RippelD at hillsboroughcounty.org>
To: <nagios-users at lists.sourceforge.net>
Subject: RE: [Nagios-users] Nagios is badly documented :(

I have to agree with Jason & John on this one. The documentation is = excellent for a piece of software as dynamic as Nagios. Nagios has been = easier to implement and customize imho than expensive commercial products = such as NetCool.

It also doesn't hurt to have an excellent user list ;)

- David.

>>> Jason Marshall <jasonm at kelman.com> 10/15/02 12:23PM >>>
I'm with you, John.  I found no shortage of detailed documentation.  WAY more than I'd ever expected to find for an open-source project like this one.

For those of you who might have missed this, look at http://www.nagios.org/docs/.  You have your choice of HTML docs online, or reading/printing a 199-page PDF document.

Some products are too powerful to do what YOU want out of the box, so a small investment of your time is required to set it up.  It's not hard -- the combination of the documentation, examples in the config files, and this list, make it a real snap, actually.


> Interesting comment...I found the docuementation to be VERY 
> complete...ma=
ybe
> too complete is the problem?  Of course, I read it ALL before I =
started.....
>=20
> -----Original Message-----
> From: doug.moore at ibill.com [mailto:doug.moore at ibill.com]=20
> Sent: Tuesday, October 15, 2002 10:49 AM
> To: nagios-users at lists.sourceforge.net=20
> Subject: [Nagios-users] Nagios is badly documented :(
>=20
>=20
> yes, Nagios is poorly documented the common user. There needs to be a  
>"paint-by-numbers" section on how to add services to nagios for one. 
>How  about a 1-2-3 to getting users proper authentication via the 
>cgi.cfg =
file?
> How about a 1-2-3 on how to setup nagios for Service Check Scheduling, 
> =
state
> types and time periods.=20
>=20
> As it stands now, a newbie has to "sift" through pages and pages of  
>documentation and config files to learn this. Trial and error... mostly  
>error and trial. =20 =20
> There is still no documentation of the relationship of the various cfg
> files. I for one still don't 100% understand how all these thing tie
> together.=20
>=20
> Nagios does have adequate install documentation but  after that if falls
> very short.  I realize that docs are the last thing anyone wants to do, =
but
> for a product as complicated as this, it really is going to have to =
produce
> them to survive in the long term.  People learn by example, nagios is  
>lacking severely in the example area for configuring major areas of the  
>program. =20 =20
> No, sorry the examples in the .cfg files don't count. Why? again, you =
don't
> know the dependencies between the cfg files. Yep, having a 
> contact-group =
of
> novell-admins doesn't do much when it isn't documented where it 
> appears =
and
> what it all effects.=20
>=20
> Not bashing the product, but just pointing out what every review of =
nagios
> states, Nagios has terrible documentation.  =20
>=20
>=20
>=20
> -----Original Message-----
> From: Anoop Atre [mailto:anoopa at hotmail.com]=20
> Sent: Tuesday, October 15, 2002 11:25 AM
> To: nagios-users at lists.sourceforge.net=20
> Subject: Re: [Nagios-users] config file
>=20
>=20
> Ok I have to object to this, I don't think nagios is that badly  
>documented.  Atleast for the initial setup and then there is -h for the 
>plugins. =20
> I installed it and had it up in at pretty much the speed with which I've
> setup
> other software (didn't even use rpms and I hear they work (mostly)
> pretty
> much out of the box)
>=20
> It just needs a little rtfm and stfw, not that I still need some help
> with certain things
> but on the whole nagios is not as bad as quite a few people make it out
> to be.
> No I am not an 'expert' of sorts, hells I don't even code as much : )
>=20
> Ethan maybe you could setup the information on the origins of the damned
> word nagios on the main nagios page (maybe a click on the word it self
> brings
> up the info..what it means, where it's from, how do you pronounce it,
> etc)
> it's just funny how every week there is that same question again : )
>=20
> I would highly recomend newbies (including moi) should read the
> following text
> put together by 'da man' (have to scroll down a bit.
> http://www.tuxedo.org/~esr/faqs/smart-questions.html=20
>=20
> ~
> ps. doesn't mean I haven't asked 'dumb' questions on this list or on
> others : )
>=20
> ----- Original Message -----
> From: <doug.moore at ibill.com>
> To: <andrewm659 at hotmail.com>; <nagios-users at lists.sourceforge.net>
> Sent: Monday, October 14, 2002 4:22 PM
> Subject: RE: [Nagios-users] config file
>=20
>=20
> > The final part of the install process creates samples for all the 
> > .cfg
> files
> > located in /usr/local/nagios/etc
> >
> > did you run
> > make all
> > make install
> > make install-init
> > make install-config
> >
> > The "install-config" will make sample config files for all the .cfg
> files
> > you need. Now, understanding how each are inter-related is another
> story!!!
> > :)
> >
> > you need more than just the nagios.cfg file to get nagios to work.
> Almost
> > every flipping .cfg file in the nagios etc directory is dependent on
> each
> > other.
> >
> > Welcome to nagios, the *worst* documented network management program
> out
> > there! :)
> >
> >
> > Once you get past the install docs (which are ok), you have to rely 
> > on
> this
> > list for the rest. There is no "here is how you add a device, follow
> the
> > these steps... 1, 2, 3, 4 docs.
> >
> > Forget about finding a document on how each file in etc is dependent
> on each
> > other and what step-by-step changes to make when adding 
> > devices/commands/services/hosts, etc.. It doesn't exist as far as I
> know.
> >
> > The guys on this list are great for support and answering questions!
> >
> > My advice, get nagios working with ONE device and service (ping is
> easy) and
> > expand out from there.  That only took me around 20 hrs!!
> >
> >
> >
> > -----Original Message-----
> > From: Andrew Meyer [mailto:andrewm659 at hotmail.com]=20
> > Sent: Monday, October 14, 2002 4:56 PM
> > To: nagios-users at lists.sourceforge.net=20
> > Subject: [Nagios-users] config file
> >
> >
> > could anyone send me there config file please.  I am confused as of
> how to
> > set one up.
> >
> > Andrew Meyer
> >
> >
> >
> > ********************************************************************
> > **
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the system manager.
> > **********************************************************************
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf=20 
> > _______________________________________________
> > Nagios-users mailing list Nagios-users at lists.sourceforge.net=20
> > https://lists.sourceforge.net/lists/listinfo/nagios-users=20
> >
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20  
>_______________________________________________
> Nagios-users mailing list  Nagios-users at lists.sourceforge.net=20
> https://lists.sourceforge.net/lists/listinfo/nagios-users=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net=20
> https://lists.sourceforge.net/lists/listinfo/nagios-users=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net=20
> https://lists.sourceforge.net/lists/listinfo/nagios-users=20
>=20

---
Jason Marshall, Unix Geek, Kelman Technologies, Inc., Calgary, AB, Canada.

  From a Sun Microsystems bug report (#4102680):
    "Workaround: don't pound on the mouse like a wild monkey."

  "I have great faith in fools:=20
     Self confidence my friends call it."  -Edgar Allan Poe




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf=20 _______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net=20
https://lists.sourceforge.net/lists/listinfo/nagios-users


--__--__--

Message: 2
From: "Carroll, Jim P [Contractor]" <jcarro10 at sprintspectrum.com>
To: nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] Nagios is badly documented :(
Date: Tue, 15 Oct 2002 11:47:06 -0500

Then we will have to agree to disagree.  I, for one, feel that the documentation for Nagios is extremely comprehensive.  It might have me scratching my head here or there (eg, service dependencies), but there's nothing that a little trial-and-error won't reveal.  Perhaps the only quibble I have on the documentation might be in terms of Nagios internals.
*shrug*

I'll grant you, the modular design of Nagios required a bit more thought to get it initially set up, and the initial pre-flight check with the default config files caused a handful of warnings and errors to spew forth which caused me some chagrin (hint: you can comment out just about everything in the sample config files; you might want to keep backup copies saved off in another directory for future reference).

You also say that Nagios is poorly documented (for) "the common user)." Maybe I'm missing something, but Nagios appears (to me) to be targetted for installation by an experienced UNIX/Linux systems administrator, not the common user.

One of the problems of the "paint-by-numbers" approach is that everyone ends up with the same picture.  Want sample config files?  They're there.  Want more examples/suggestions?  That's what this mailing list is for.

Looking for help configuring Apache?  That's not really what Nagios or this mailing list is about, but you might find someone willing to help you there.

Looking for help configuring Sendmail so you can get your notifications? Again, that's not really what Nagios/this mailing list is about, but you might find someone (like myself) willing to help out.

Nagios is vast, of that there is no doubt.  If you feel you're qualified to do the installation, then by all means, hang in there; frustration is a sign that success is just around the corner.  :)

jc

> -----Original Message-----
> From: doug.moore at ibill.com [mailto:doug.moore at ibill.com]
> Sent: Tuesday, October 15, 2002 10:49 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios is badly documented :(
> 
> 
> yes, Nagios is poorly documented the common user. There needs to be a 
> "paint-by-numbers" section on how to add services to nagios for one. 
> How about a 1-2-3 to getting users proper authentication via the
> cgi.cfg file?
> How about a 1-2-3 on how to setup nagios for Service Check 
> Scheduling, state
> types and time periods. 
> 
> As it stands now, a newbie has to "sift" through pages and pages of 
> documentation and config files to learn this. Trial and error... 
> mostly error and trial.
> 
> There is still no documentation of the relationship of the various cfg 
> files. I for one still don't 100% understand how all these thing tie 
> together.
> 
> Nagios does have adequate install documentation but  after
> that if falls
> very short.  I realize that docs are the last thing anyone 
> wants to do, but
> for a product as complicated as this, it really is going to 
> have to produce
> them to survive in the long term.  People learn by example, nagios is
> lacking severely in the example area for configuring major 
> areas of the
> program.  
> 
> No, sorry the examples in the .cfg files don't count. Why?
> again, you don't
> know the dependencies between the cfg files. Yep, having a 
> contact-group of
> novell-admins doesn't do much when it isn't documented where 
> it appears and
> what it all effects. 
> 
> Not bashing the product, but just pointing out what every
> review of nagios
> states, Nagios has terrible documentation.   
> 
> 
> 
> -----Original Message-----
> From: Anoop Atre [mailto:anoopa at hotmail.com]
> Sent: Tuesday, October 15, 2002 11:25 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] config file
> 
> 
> Ok I have to object to this, I don't think nagios is that badly 
> documented. Atleast for the initial setup and then there is -h for the 
> plugins.
> 
> I installed it and had it up in at pretty much the speed with
> which I've
> setup
> other software (didn't even use rpms and I hear they work (mostly)
> pretty
> much out of the box)
> 
> It just needs a little rtfm and stfw, not that I still need some help 
> with certain things but on the whole nagios is not as bad as quite a 
> few people make it out
> to be.
> No I am not an 'expert' of sorts, hells I don't even code as much : )
> 
> Ethan maybe you could setup the information on the origins of
> the damned
> word nagios on the main nagios page (maybe a click on the word it self
> brings
> up the info..what it means, where it's from, how do you pronounce it,
> etc)
> it's just funny how every week there is that same question again : )
> 
> I would highly recomend newbies (including moi) should read the 
> following text put together by 'da man' (have to scroll down a bit.
> http://www.tuxedo.org/~esr/faqs/smart-questions.html
> 
> ~
> ps. doesn't mean I haven't asked 'dumb' questions on this list or on 
> others : )
> 
> ----- Original Message -----
> From: <doug.moore at ibill.com>
> To: <andrewm659 at hotmail.com>; <nagios-users at lists.sourceforge.net>
> Sent: Monday, October 14, 2002 4:22 PM
> Subject: RE: [Nagios-users] config file
> 
> 
> > The final part of the install process creates samples for
> all the .cfg
> files
> > located in /usr/local/nagios/etc
> >
> > did you run
> > make all
> > make install
> > make install-init
> > make install-config
> >
> > The "install-config" will make sample config files for all the .cfg
> files
> > you need. Now, understanding how each are inter-related is another
> story!!!
> > :)
> >
> > you need more than just the nagios.cfg file to get nagios to work.
> Almost
> > every flipping .cfg file in the nagios etc directory is dependent on
> each
> > other.
> >
> > Welcome to nagios, the *worst* documented network management program
> out
> > there! :)
> >
> >
> > Once you get past the install docs (which are ok), you have
> to rely on
> this
> > list for the rest. There is no "here is how you add a device, follow
> the
> > these steps... 1, 2, 3, 4 docs.
> >
> > Forget about finding a document on how each file in etc is dependent
> on each
> > other and what step-by-step changes to make when adding 
> > devices/commands/services/hosts, etc.. It doesn't exist as far as I
> know.
> >
> > The guys on this list are great for support and answering questions!
> >
> > My advice, get nagios working with ONE device and service (ping is
> easy) and
> > expand out from there.  That only took me around 20 hrs!!
> >
> >
> >
> > -----Original Message-----
> > From: Andrew Meyer [mailto:andrewm659 at hotmail.com]
> > Sent: Monday, October 14, 2002 4:56 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] config file
> >
> >
> > could anyone send me there config file please.  I am confused as of
> how to
> > set one up.
> >
> > Andrew Meyer
> >
> >
> >
> > 
> **********************************************************************
> > This email and any files transmitted with it are confidential and 
> > intended solely for the use of the individual or entity to whom they 
> > are addressed. If you have received this email in error
> please notify
> > the system manager.
> > 
> **********************************************************************
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf 
> > _______________________________________________
> > Nagios-users mailing list Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> >
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> 


--__--__--

Message: 3
Date: Tue, 15 Oct 2002 11:02:35 -0600
Subject: Re: [Nagios-users] Nagios is badly documented :(
From: Terry Simons <galimore at mac.com>
To: nagios-users at lists.sourceforge.net

I agree...

I read all of the documentation also and it was very helpful. I have 
also found that most of the questions asked on this list are in the 
documentation... it does require a bit of effort though.

- Terry


On Tuesday, October 15, 2002, at 10:02 AM, Jolet, John wrote:

> Interesting comment...I found the docuementation to be VERY 
> complete...maybe
> too complete is the problem?  Of course, I read it ALL before I 
> started.....
>
> -----Original Message-----
> From: doug.moore at ibill.com [mailto:doug.moore at ibill.com]
> Sent: Tuesday, October 15, 2002 10:49 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios is badly documented :(
>
>
> yes, Nagios is poorly documented the common user. There needs to be a
> "paint-by-numbers" section on how to add services to nagios for one. 
> How
> about a 1-2-3 to getting users proper authentication via the cgi.cfg 
> file?
> How about a 1-2-3 on how to setup nagios for Service Check Scheduling, 
> state
> types and time periods.
>
> As it stands now, a newbie has to "sift" through pages and pages of
> documentation and config files to learn this. Trial and error... mostly
> error and trial.
>
> There is still no documentation of the relationship of the various cfg
> files. I for one still don't 100% understand how all these thing tie
> together.
>
> Nagios does have adequate install documentation but  after that if 
> falls
> very short.  I realize that docs are the last thing anyone wants to 
> do, but
> for a product as complicated as this, it really is going to have to 
> produce
> them to survive in the long term.  People learn by example, nagios is
> lacking severely in the example area for configuring major areas of the
> program.
>
> No, sorry the examples in the .cfg files don't count. Why? again, you 
> don't
> know the dependencies between the cfg files. Yep, having a 
> contact-group of
> novell-admins doesn't do much when it isn't documented where it 
> appears and
> what it all effects.
>
> Not bashing the product, but just pointing out what every review of 
> nagios
> states, Nagios has terrible documentation.
>
>
>
> -----Original Message-----
> From: Anoop Atre [mailto:anoopa at hotmail.com]
> Sent: Tuesday, October 15, 2002 11:25 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] config file
>
>
> Ok I have to object to this, I don't think nagios is that badly
> documented.
> Atleast for the initial setup and then there is -h for the plugins.
>
> I installed it and had it up in at pretty much the speed with which 
> I've
> setup
> other software (didn't even use rpms and I hear they work (mostly)
> pretty
> much out of the box)
>
> It just needs a little rtfm and stfw, not that I still need some help
> with certain things
> but on the whole nagios is not as bad as quite a few people make it out
> to be.
> No I am not an 'expert' of sorts, hells I don't even code as much : )
>
> Ethan maybe you could setup the information on the origins of the 
> damned
> word nagios on the main nagios page (maybe a click on the word it self
> brings
> up the info..what it means, where it's from, how do you pronounce it,
> etc)
> it's just funny how every week there is that same question again : )
>
> I would highly recomend newbies (including moi) should read the
> following text
> put together by 'da man' (have to scroll down a bit.
> http://www.tuxedo.org/~esr/faqs/smart-questions.html
>
> ~
> ps. doesn't mean I haven't asked 'dumb' questions on this list or on
> others : )
>
> ----- Original Message -----
> From: <doug.moore at ibill.com>
> To: <andrewm659 at hotmail.com>; <nagios-users at lists.sourceforge.net>
> Sent: Monday, October 14, 2002 4:22 PM
> Subject: RE: [Nagios-users] config file
>
>
>> The final part of the install process creates samples for all the cfg
> files
>> located in /usr/local/nagios/etc
>>
>> did you run
>> make all
>> make install
>> make install-init
>> make install-config
>>
>> The "install-config" will make sample config files for all the .cfg
> files
>> you need. Now, understanding how each are inter-related is another
> story!!!
>> :)
>>
>> you need more than just the nagios.cfg file to get nagios to work.
> Almost
>> every flipping .cfg file in the nagios etc directory is dependent on
> each
>> other.
>>
>> Welcome to nagios, the *worst* documented network management program
> out
>> there! :)
>>
>>
>> Once you get past the install docs (which are ok), you have to rely on
> this
>> list for the rest. There is no "here is how you add a device, follow
> the
>> these steps... 1, 2, 3, 4 docs.
>>
>> Forget about finding a document on how each file in etc is dependent
> on each
>> other and what step-by-step changes to make when adding
>> devices/commands/services/hosts, etc.. It doesn't exist as far as I
> know.
>>
>> The guys on this list are great for support and answering questions!
>>
>> My advice, get nagios working with ONE device and service (ping is
> easy) and
>> expand out from there.  That only took me around 20 hrs!!
>>
>>
>>
>> -----Original Message-----
>> From: Andrew Meyer [mailto:andrewm659 at hotmail.com]
>> Sent: Monday, October 14, 2002 4:56 PM
>> To: nagios-users at lists.sourceforge.net
>> Subject: [Nagios-users] config file
>>
>>
>> could anyone send me there config file please.  I am confused as of
> how to
>> set one up.
>>
>> Andrew Meyer
>>
>>
>>
>> **********************************************************************
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they
>> are addressed. If you have received this email in error please notify
>> the system manager.
>> **********************************************************************
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users



--__--__--

Message: 4
Date: Tue, 15 Oct 2002 18:09:03 +0100
To: nagios-users at lists.sourceforge.net
From: Raymond Brighenti <ray at corpex.com>
Subject: RE: [Nagios-users] Nagios is badly documented :(


I found this article which gets you up and running nicely without having to 
do too much reading of the docs to start off with.
http://www.onlamp.com/pub/a/onlamp/2002/09/05/nagios.html

Then once I'd completed it and had the basics up and going and had a start 
to understanding the ins and outs you hit the docs and with a bit of trial 
and error was plowing through the more advanced stuff.

Have to agree, has to be one of the most comprehensive and configurable 
pieces of work I've come across!

Ray

At 11:47 15/10/2002 -0500, you wrote:
>Then we will have to agree to disagree.  I, for one, feel that the
>documentation for Nagios is extremely comprehensive.  It might have me
>scratching my head here or there (eg, service dependencies), but there's
>nothing that a little trial-and-error won't reveal.  Perhaps the only
>quibble I have on the documentation might be in terms of Nagios internals.
>*shrug*
>
>I'll grant you, the modular design of Nagios required a bit more thought to
>get it initially set up, and the initial pre-flight check with the default
>config files caused a handful of warnings and errors to spew forth which
>caused me some chagrin (hint: you can comment out just about everything in
>the sample config files; you might want to keep backup copies saved off in
>another directory for future reference).
>
>You also say that Nagios is poorly documented (for) "the common user)."
>Maybe I'm missing something, but Nagios appears (to me) to be targetted for
>installation by an experienced UNIX/Linux systems administrator, not the
>common user.
>
>One of the problems of the "paint-by-numbers" approach is that everyone ends
>up with the same picture.  Want sample config files?  They're there.  Want
>more examples/suggestions?  That's what this mailing list is for.
>
>Looking for help configuring Apache?  That's not really what Nagios or this
>mailing list is about, but you might find someone willing to help you there.
>
>Looking for help configuring Sendmail so you can get your notifications?
>Again, that's not really what Nagios/this mailing list is about, but you
>might find someone (like myself) willing to help out.
>
>Nagios is vast, of that there is no doubt.  If you feel you're qualified to
>do the installation, then by all means, hang in there; frustration is a sign
>that success is just around the corner.  :)
>
>jc
>
> > -----Original Message-----
> > From: doug.moore at ibill.com [mailto:doug.moore at ibill.com]
> > Sent: Tuesday, October 15, 2002 10:49 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Nagios is badly documented :(
> >
> >
> > yes, Nagios is poorly documented the common user. There needs to be a
> > "paint-by-numbers" section on how to add services to nagios
> > for one. How
> > about a 1-2-3 to getting users proper authentication via the
> > cgi.cfg file?
> > How about a 1-2-3 on how to setup nagios for Service Check
> > Scheduling, state
> > types and time periods.
> >
> > As it stands now, a newbie has to "sift" through pages and pages of
> > documentation and config files to learn this. Trial and
> > error... mostly
> > error and trial.
> >
> > There is still no documentation of the relationship of the various cfg
> > files. I for one still don't 100% understand how all these thing tie
> > together.
> >
> > Nagios does have adequate install documentation but  after
> > that if falls
> > very short.  I realize that docs are the last thing anyone
> > wants to do, but
> > for a product as complicated as this, it really is going to
> > have to produce
> > them to survive in the long term.  People learn by example, nagios is
> > lacking severely in the example area for configuring major
> > areas of the
> > program.
> >
> > No, sorry the examples in the .cfg files don't count. Why?
> > again, you don't
> > know the dependencies between the cfg files. Yep, having a
> > contact-group of
> > novell-admins doesn't do much when it isn't documented where
> > it appears and
> > what it all effects.
> >
> > Not bashing the product, but just pointing out what every
> > review of nagios
> > states, Nagios has terrible documentation.
> >
> >
> >
> > -----Original Message-----
> > From: Anoop Atre [mailto:anoopa at hotmail.com]
> > Sent: Tuesday, October 15, 2002 11:25 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: Re: [Nagios-users] config file
> >
> >
> > Ok I have to object to this, I don't think nagios is that badly
> > documented.
> > Atleast for the initial setup and then there is -h for the plugins.
> >
> > I installed it and had it up in at pretty much the speed with
> > which I've
> > setup
> > other software (didn't even use rpms and I hear they work (mostly)
> > pretty
> > much out of the box)
> >
> > It just needs a little rtfm and stfw, not that I still need some help
> > with certain things
> > but on the whole nagios is not as bad as quite a few people
> > make it out
> > to be.
> > No I am not an 'expert' of sorts, hells I don't even code as much : )
> >
> > Ethan maybe you could setup the information on the origins of
> > the damned
> > word nagios on the main nagios page (maybe a click on the word it self
> > brings
> > up the info..what it means, where it's from, how do you pronounce it,
> > etc)
> > it's just funny how every week there is that same question again : )
> >
> > I would highly recomend newbies (including moi) should read the
> > following text
> > put together by 'da man' (have to scroll down a bit.
> > http://www.tuxedo.org/~esr/faqs/smart-questions.html
> >
> > ~
> > ps. doesn't mean I haven't asked 'dumb' questions on this list or on
> > others : )
> >
> > ----- Original Message -----
> > From: <doug.moore at ibill.com>
> > To: <andrewm659 at hotmail.com>; <nagios-users at lists.sourceforge.net>
> > Sent: Monday, October 14, 2002 4:22 PM
> > Subject: RE: [Nagios-users] config file
> >
> >
> > > The final part of the install process creates samples for
> > all the .cfg
> > files
> > > located in /usr/local/nagios/etc
> > >
> > > did you run
> > > make all
> > > make install
> > > make install-init
> > > make install-config
> > >
> > > The "install-config" will make sample config files for all the cfg
> > files
> > > you need. Now, understanding how each are inter-related is another
> > story!!!
> > > :)
> > >
> > > you need more than just the nagios.cfg file to get nagios to work.
> > Almost
> > > every flipping .cfg file in the nagios etc directory is dependent on
> > each
> > > other.
> > >
> > > Welcome to nagios, the *worst* documented network management program
> > out
> > > there! :)
> > >
> > >
> > > Once you get past the install docs (which are ok), you have
> > to rely on
> > this
> > > list for the rest. There is no "here is how you add a device, follow
> > the
> > > these steps... 1, 2, 3, 4 docs.
> > >
> > > Forget about finding a document on how each file in etc is dependent
> > on each
> > > other and what step-by-step changes to make when adding
> > > devices/commands/services/hosts, etc.. It doesn't exist as far as I
> > know.
> > >
> > > The guys on this list are great for support and answering questions!
> > >
> > > My advice, get nagios working with ONE device and service (ping is
> > easy) and
> > > expand out from there.  That only took me around 20 hrs!!
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Andrew Meyer [mailto:andrewm659 at hotmail.com]
> > > Sent: Monday, October 14, 2002 4:56 PM
> > > To: nagios-users at lists.sourceforge.net
> > > Subject: [Nagios-users] config file
> > >
> > >
> > > could anyone send me there config file please.  I am confused as of
> > how to
> > > set one up.
> > >
> > > Andrew Meyer
> > >
> > >
> > >
> > >
> > **********************************************************************
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity to whom they
> > > are addressed. If you have received this email in error
> > please notify
> > > the system manager.
> > >
> > **********************************************************************
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Nagios-users mailing list
> > > Nagios-users at lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> >
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Nagios-users mailing list
>Nagios-users at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nagios-users
>______________________________________________________________________________
>This email has been checked for viruses by ArmourPlate,
>http://www.armourplate.com, the multi-scanner anti-virus facility from Corpex.

Corpex Limited  * email virus protection * Server Co-Location
UK & Germany    * Web Site Hosting * Domain Name Services
http://www.corpex.com   T +44 (0)207 430 8000 F +44(0)207 430 8099
_____________________________________________________________________
This message has been checked for viruses by Corpex
using the ArmourPlate Virus Scanning Service. To find out
how to protect your company visit http://www.armourplate.com
or call Corpex on +44 (0)207 430 8000.




--__--__--

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users


End of Nagios-users Digest


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf




More information about the Users mailing list