When updating the influxdb container we always experience a down time for the moment when the volume is moved from one to the other container. During that time logs are not making it to the influxdb. Unfortunately the handler does not resend them once the influxdb is up and running again.
Therefore I would like to request the implementation of a submit successful check that caches entries in case that the submit did not complete successful and tries to resend them every x-seconds for example.
When updating the influxdb container we always experience a down time for the moment when the volume is moved from one to the other container. During that time logs are not making it to the influxdb. Unfortunately the handler does not resend them once the influxdb is up and running again.
Therefore I would like to request the implementation of a submit successful check that caches entries in case that the submit did not complete successful and tries to resend them every x-seconds for example.