Blogpost would be awesome, looking forward to this as well :) On 10/8-August/2015 1:01 PM, Andreas Lehr wrote: > Blogpost would be nice as always. > Looking forward to it :) > > > 2015-08-10 11:42 GMT+02:00 Martin Stiborský <martin.stibor...@gmail.com > <mailto:martin.stibor...@gmail.com>>: > > Ok, got it working now… > After all, I've used the config synchronization and that was the > key…it looks good. Now I have to put it all in to chef recipes, so > I'll go through all of it once again and I hope to collect my notes > into some meaningful format, so I can publish it as a blogpost or > something. > > On Sun, Aug 9, 2015 at 1:10 PM Martin Stiborský > <martin.stibor...@gmail.com <mailto:martin.stibor...@gmail.com>> wrote: > > Hello guys, > after few weeks of solving netwoking problems with our provider, > I'm finally able to start putting together "distributed" > monitoring for our infrastructure. > > Starting lightly, this is the current target: > > Icinga master, just one for now, sitting on our premises, > currently monitoring just itself and few other machines via > icinga2 client installed on them and using the "command > endpoint" property. This works. > > Now, to monitor the vitual machines hosted on the provider's > site, we will have a satellite icinga instance, which will > monitor the hosts there, that's the part I don't fully understand. > The idea is that these two icinga instances, the master and the > satellite, are independent, meaning if there is a network > problem between the master and the satellite, the monitoring > still goes on, nothing break, the log is replayed to the master > once the network works again. > Sound good. > > So the problem is - what is needed to do in order to make the > satellite sending monitoring data to the master? > I have to create a zone and an endpoint for the satellite, > that's clear, this part works - I can see from the icinga2.log > and also in the cluster health check that the satellite endpoint > is connected. Api listener feature is configured as well. > > Now if I just configure few checks for the satellite itself, the > configs are modified on the satellite icinga2 installation, are > these data automatically send to the master? > Because in the zone configuration, the master is parent of the > satellite, is that how it works? > I don't know, I've tried, but it doesn't work for me this way. > Do I have to specify the host/commands/services configuration > for the satellite on the master instance? Or is it enough to > have in only on the satellite? > I guess both…but I'm not sure. > > I don't know, because if I mix here the "command endpoint" thing > to invoke a check on the satellite, then it doesn't look much > like an "independent" to me. > > I don't want to bring here any zones sync now, that's another > level of abstractions I think, I need to understand basics first. > > Sure I have the documentation opened, the vagrant boxes too, but > I can't wrap my brain around it. > > Any hints welcomed, > btw, thanks for all your work guys, it's fun to work with icinga2. > > Thanks! > > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > https://lists.icinga.org/mailman/listinfo/icinga-users > > > > > -- > > Andreas Lehr > > m...@andreas-lehr.com <mailto:m...@andreas-lehr.com> > twitter.com/shakalandy <http://twitter.com/shakalandy> > > > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users >
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
