On 25.10.2013 14:56, Adrián López wrote: > > > If you want to have a single dashboard to monitorice several icinga > core instances,
you may also just use icinga core, idoutils and icinga web provided by the native icinga stack. you may also use the shared database involved in that setup for icinga reporting then. but it's also reasonable to have remote checkers (could just be a master/slave setup of icinga instances too) and only the master collects all checkresults and presents that in an aggregated view. if it shouldn't happen on the same server, just e.g. stash the data into the idoutils database and grant the remote webserver read only access to it. -- 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 ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
