Filebeat temporarily unable to connect to ES

If Filebeat, running as a service, cannot temporarily connect to the destination Elasticsearch instance then what is the process?
Does it continually retry until the destination is available?
Does it just error out?

Is there any documentation of the process?

Yes.

No. It will write to the internal queue if you have this configured and will then stop reading data in order to avoid data loss until it is again able to send data.

'No. It will write to the internal queue if you have this configured and will then stop reading data in order to avoid data loss until it is again able to send data.'

Where would this internal queue be configured?

Seems like I forgot to include the link. Have updated my previous post.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.