Improving logstash data resiliency


The documentation on Logstash about persisten queues says:

It does not handle permanent machine failures such as disk corruption, disk failure, and machine loss. The data persisted to disk is not replicated.

So what strategies can be deployed to remediate that? How can I ensure the events will be persisted even in the case of a hardware failures?

Let's say I have access two data centers and I want 100% of the events sent to be persisted as long as at least one of the two datacenters is available. How should logstash be deployed?

(system) #2

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