(Surendra Kotte) #1


Do we have a way to configure failover for filebeat process?

Thanks in advance!


(Jaime Soriano) #2

Hi @surendrakotte,

What do you mean by a failover for filebeat process?

(Surendra Kotte) #3

Yes, like a secondary process to take over the processing incase primary fails.

(Jaime Soriano) #4

Filebeat is deployed in all nodes, and in each one of them it keeps a registry with the logs read and succesfully sent, so no data should be lost if the process is restarted. In principle it shouldn't "fail" or stop unexpectedly (if it does it should be considered a bug, so please report it :slight_smile:). If you are using a service manager (like systemd in Linux) to start filebeat you can configure it to restart the process automatically if it stops unexpectedly.

You can also configure multiple hosts in the output, so if one fail another one can be used.

Filebeat 6.3 will have a new spooling feature (in beta) that will store events locally on disk if all the hosts in the output are down, so they can be sent when the hosts are back online.

I hope it helps to answer your question, if you have a more specific question or about an specific scenario please ask :slight_smile:

(Surendra Kotte) #5

Hi Jaime,

Thanks for explaining it to me! Can you let me know when 6.3 is generally available?

(Jaime Soriano) #6

I cannot confirm a specific date, but we expect to release 6.3 really soon.

(system) #7

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