You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2022. It is now read-only.
Just curious, if the brokers aren't available, do we eventually lose logs with this solution? For example using a log tailer like Filebeat or Fluent.D thos mecanism will keep track their place and retry as needed.
The text was updated successfully, but these errors were encountered:
There is no automatism that would retain and retransmit logs that could not be delivered directly. You MAY use a fallback-appender (ref to readme) that would send log messages somewhere else where they might be stored and retransmitted later.
Example: My original use case was to append logs from read-only containers to kafka. So as long as Kafka was available, the container would publish it's logs to kafka. If there was an broker outage, it's log messages would be sent to the fallback-appender. The fallback appender in this case would be a console.err appender that would be picked up by the docker logging driver and act as a fallback.
Just curious, if the brokers aren't available, do we eventually lose logs with this solution? For example using a log tailer like Filebeat or Fluent.D thos mecanism will keep track their place and retry as needed.
The text was updated successfully, but these errors were encountered: