Marco, I will check it, many thanks to provide such info. Main reason for my use is similiar to yours - manage downtimes from deployment automation environment.
With regards .zp. On Tue, Jan 21, 2014 at 4:46 PM, Marco Hoyer <[email protected]> wrote: > Jo Zdenek, > > you could try the following I replied to a similar question some days > before: > > We implemented a http exporter service for mk_livestatus socket and > icinga.cmd file. We use it for our deployment automation tool to schedule a > downtime for hosts during deployment. > It is also used to transport commands from remote icinga-web instances to > multiple icinga instances (much better than SSH in our environment). > > If you are interested: > http://mathias-kettner.de/checkmk_livestatus.html > https://github.com/ImmobilienScout24/livestatus_service > https://github.com/marco-hoyer/icinga-web-module-http-console-connection > > Kind regards, > Marco > > > Am 21.01.2014 um 14:33 schrieb Zdenek Pizl <[email protected]>: > > Hallo, > > is there any tutorial how to manage monitored nodes using REST API or if > is it even possible to set i.e. scheduled downtime or acknowledge an issue > via REST PAI ? > > I am using v1.10.2 currently but I am not successful when searching for it > at all. Thank you for help or some cute URLs with plenty of ideas and > information, .zp. > > > -- > > Zdenek Pizl > [email protected] > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users > > > > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users > > -- Zdenek Pizl [email protected]
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
