Hi, > On 5 May 2017, at 15:38, Valentin Höbel <[email protected]> > wrote: > > Hi Michael, > > ok, thanks for the fast reply! > > In your eyes: Would it make sense to open an issue on GitHub regarding > buffering the data of failed writes (to InfluxDB)?
You can always do that. Best would be to sponsor development time for this feature. Kind regards, Michael > > Best regards > Valentin > > On 04.05.2017 11:15, Michael Friedrich wrote: >>> On 4 May 2017, at 11:08, Valentin Höbel <[email protected]> >>> 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 >> >> > > -- > 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 > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
