You can find informations over there : https://docs.icinga.com/icinga2/latest/doc/module/icinga2/chapter/distributed-monitoring?highlight-search=log_duration#distributed-monitoring-advanced-hints-command-endpoint-log-duration
log_duration attribute can be used to define how many time you want to store logs on the client side. The size of the file will depend on how many checks you have and also the frequency of each check. 2017-03-29 19:56 GMT+02:00 Antony Stone <antony.st...@icinga.open.source.it> : > Hi. > > I'm aware that when Icinga2 is configured in top-down config sync mode, the > remote machine (client or satellite, as the case may be) will continue > performing checks and logging results locally in the event of a > connectivity > failure between that machine and its parent. > > What I'm trying to find out is how large is the backlog buffer for storing > results for later transfer back to the parent when connectivity is > restored. > > What settings are available (and in which config file) to define how much > data > (or what duration of results?) gets stored on the client / satellite for > later > transfer to the parent? > > > Thanks, > > > Antony. > > -- > If you can smile when all about you things are going wrong, you must have > someone in mind to take the blame. > > Please reply to the > list; > please *don't* CC > me. > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users > -- *Pierrick CHOVELON* *Département Infrastructure Hardware * *Apprenti Ingénieur* *www.a-sis.fr * <http://www.a-sis.fr/>
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
