Michael, Thank you for your suggestion!
I am very interested to find out about "For 2.4 later this year we're targetting a general api, still in early concept phasis." Nobuo Date: Tue, 5 May 2015 08:12:12 +0200 From: Michael Friedrich <michael.friedr...@netways.de<mailto:michael.friedr...@netways.de>> To: <icinga-users@lists.icinga.org<mailto:icinga-users@lists.icinga.org>> Subject: Re: [icinga-users] Icinga2 -- what do you suggest? Message-ID: <55485f3c.6090...@netways.de<mailto:55485f3c.6090...@netways.de>> Content-Type: text/plain; charset="utf-8"; Format="flowed" Am 05.05.2015 um 06:13 schrieb stefano bianchi: Nobuto for first question you can just execute a remote cmd from host to icinga as suggested in https://mathias-kettner.de/checkmk_livestatus.html look for Remote access to Livestatus via SSH or xinetd (i suggest to use livestatus instead to icinga.cmd). That's not really necessary as Icinga 2's livestatus feature also supports tcp sockets (different to the 1.x addon). Although I wouldn't recomment opening that port without proper authentication - I prefer native SSH and the command pipe (if that's the one you are using for Icinga Web 1/2 or Classic UI already). For 2.4 later this year we're targetting a general api, still in early concept phasis. You also may run a custom script to add your new servers and theirs services to config from templates at end of kick start / puppet. There's a puppet module in the making, you might want to check it out and help test/finalize its 1.0.0 release. Kind regards, Michael
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
