On 13.09.2013 00:23, Adrián López Tejedor wrote:
> In a environment, where we want a central monitoring, with hundreds of hosts
> divided into proyects, and new ones joining each month. How could be handle
> the need of changing configurations?
i'd create a global configuration folder which gets included. below that
i would have all projects listed. if one isn't available, mv the folder
away. or cp a new folder for the projects config files into it, and
verify configuration/reload icinga core.
i.e.
# mkdir /etc/icinga/generated
# vim /etc/icinga/icinga.cfg
cfg_dir=/etc/icinga/generated
# mkdir -p /etc/icinga/generated/{project1,project2,project3}
>
> Every day some proyect needs to change something, and restart the server
> means stop the monitoring for several minutes, and it should be 24x7.
use icinga (idoutils) 1.9.3 and reload on config changes.
>
> Ideas in how to deal with this?
if you're using a native configuration gui, i would use lconf, and
organise each project in a seperate tree.
- main
----- projects
--------- project1
--------------linuxservers
--------- project1
--------------linuxservers
--------------windowsservers
adding a new project could be done via drag&drop from an existing
project tree (or create a new structural object). deletion is easy too.
generating the configuration and reloading icinga core then could be
done via gui as well. (plus, you may define attributes in 'projects'
being inherited to all projects below, i.e. default notification admin,
or check interval', which can be overridden locally in each project)
different idea:
use puppet manifests to generate the icinga configuration, and add
projects as nodes, having specified hosts below.
kind regards,
michael
>
> Thanks!
>
> P.S.: sorry about my english
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
> nuestra política de envío y recepción de correo electrónico en el enlace
> situado más abajo.
> This message is intended exclusively for its addressee. We only send and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> 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
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
