Queues and data resiliency

By default, Logstash uses in-memory bounded queues between pipeline stages (inputs → pipeline workers) to buffer events.

As data flows through the event processing pipeline, Logstash may encounter situations that prevent it from delivering events to the configured output. For example, the data might contain unexpected data types, or Logstash might terminate abnormally.

To guard against data loss and ensure that events flow through the pipeline without interruption, Logstash provides data resiliency features.

These resiliency features are disabled by default. To turn on these features, you must explicitly enable them in the Logstash settings file.