On 20.04.2013 03:30, Jim Miller wrote:
>
> I really don’t get the thought process for the location of files in
> /ect/icinga/*.
>
> If you’re going to have ‘SAMPLE’ files.. why are they put into the
> ‘production’ directory? Do I use those sample files? Do I move them
> somewhere else and create new ones.
>
icinga can be installed in 5 minutes, providing sample configuration for
monitoring localhost. which is a good thing, as most people forget to
monitor their monitoring host, and then wondering why icinga does not
work anymore because log's disk is full. so basically those sample files
even provide you with the power of a basic localhost monitoring, easily
extendable by your own configuration.
even icinga2 will contain and provide some basic configuration for the
host where it is running on. at least that's what you get when
installing the dev version from git right on. the idea is the same like
in icinga 1.x - samples for localhost monitoring, but also templates for
further usage. we call it 'itl', which means 'icinga template library'.
you may also recognize the existing templates in the icinga 1.x
configuration (register 0) and likely you are using them all over ('use
generic-service'). but if you have chosen to roll you very own
configuration, it's easy to do so - since you pass the icinga.cfg to the
icinga binary on startup, you'll define all includes over there. if you
do not like objects/ oder conf.d/ to be included, then define something
else. but always remember - if dropping sample configuration, you may
miss out some details. so once you do, make sure to have read the
documentation on the configuration, and understood how it works and how
it's organized.
kind regards,
Michael
> *From:*Jim Miller
> *Sent:* Friday, April 19, 2013 7:54 PM
> *To:* icinga-users@lists.sourceforge.net
> *Subject:* [icinga-users] Noob to icinga but not nagios
>
> Hi everyone,
>
> Please don’t spam me too much for sending this email. It’s been a few
> years since I’ve setup nagios and I’ve forgotten more than I remember.
> I decided to go with icinga over nagios because of all the hard work
> that’s gone into the fork.
>
> I would really like to just buy a good book that documents ‘best
> practices’ for setting up icinga. Like a good/best practice for
> setting up contacts, notifications, remote hosts, services, nrpe, etc.
> etc. I’m REALLY not trying to shirk reading the online docs which are
> good but a little too general and I just don’t have time with all my
> other tasks.
>
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis& visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
>
>
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-users
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
