[icinga-users] keeping Icinga configurations in sync

Isaac Witmer isaac.witmer at vistashare.com
Fri Mar 16 15:50:02 CET 2012


The current setup is two Icinga servers, one in a local network, and
one outside in cyberspace.
There are several servers in the local network that are checked by the
local instance of Icinga, but the notifications and external servers
are (for the most part) handled by the external instance.

This causes some issues for keeping configurations in sync. If a new
computer is added to the local network, a new configuration has to be
added to the local Icinga, and then another almost identical
configuration (except marked as passive:
http://docs.icinga.org/1.0.1/en/passivechecks.html)  on the external
host.
It's not quite as simple as simply copying the configurations between
incinga servers, though, because one server can check the hosts and
the other can't (firewall restrictions prevent the external server
from accessing internal hosts).

I've thought a bit about modifying the templates so that I can make
the configurations in the template, but that doesn't quite work
either. The issue being that host configurations are preferred to
template configurations (understandably), meaning that I can't copy
host configurations from the local instance to the external instance
and expect the external instance to use a different (simply return
critical when it doesn't get any alerts) check command.

Am I making any sense? Are there any ideas/documentation that would
make this easier?

One idea that might help would be to attempt to script some things to
output the configuration files that I need... Are there tools out
there that do that already?

-- 
Isaac Witmer
www.VistaShare.com
www.facebook.com/vistashare




More information about the icinga-users mailing list