> On 4 May 2017, at 11:08, Valentin Höbel <v.hoe...@openinfrastructure.de> > wrote: > > Dear list, > > I am playing around with Icinga2 and InfluxDB. > > My setup: > Icinga2 -> InfluxDB-Feature -> InfluxDB > > I noticed that when InfluxDB is not available, Icinga2 seems not to buffer > failed writes. Instead, all values are lost when I e.g. shut down InfluxDB > for two minutes. > > Is there a way to let Icinga2 buffer all writes until InfluxDB is available > again?
No, currently that’s not possible. You would need a caching relay in the middle, afaik carbon-cache-ng for Graphite does a similar thing. I don’t know if that exists for InfluxDB. Kind regards, Michael > > > In addition, I added InfluxDB-Relay to the chain: > > Icinga2 -> InfluxDB-Feature -> InfluxDB-Relay -> InfluxDB > > My hope was that, if properly configured, InfluxDB-Relay buffers failed > writes. However, my tests show that this is not the case (although it is > supposed to work). Did someone experience something similar? > > My goal is to somehow "save" the metrics if InfluxDB is down for a couple of > minutes. I am thinking of setting up a MessageBus and let Icinga2 write the > metrics there; however, I would like to avoid that construct. > > Best regards, > Valentin > > -- > Valentin Höbel > Senior Consultant IT Infrastructure > mobil 0711-95337077 > > Linux Information Systems > LIS Stuttgart GmbH > Talstraße 41 70188 Stuttgart Germany > > Geschäftsführer Tilo Mey > Amtsgericht Stuttgart, HRB 729287, Ust-IdNr DE264295269 > Volksbank Stuttgart EG, BIC VOBADESS, IBAN DE75600901000340001003 > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
