Diagnosing Logstash Persistent Queue Disk Saturation and Backpressure
Identify why Logstash throughput collapses when the persistent queue fills, verify disk and config causes, apply targeted fixes, and know when to escalate.
Loading…
ReadMeFeed / Community knowledge
#persistent-queue
Real questions. Useful conversations. Find the people who know your stack.
logstash
elasticsearchConfiguring Logstash Persistent Queues for Production Durability
Enable Logstash persistent queues to survive crashes, configure disk size and checkpoint frequency, monitor usage via the API, and avoid common pitfalls like network storage or shared queue directories.
Choosing Between Logstash In‑Memory and Persistent Queues for At‑Least‑Once Delivery
Guide to deciding when to enable Logstash persistent queues for at‑least‑once delivery, with configuration steps, trade‑offs and validation.
Using Logstash Persistent Queues to Prevent Data Loss on Restart
Learn how to enable Logstash persistent queues, configure them, and verify they survive a crash without losing events.
Persistent Queues in Logstash: Turning Volatile Buffers into Durable Storage
Learn how Logstash’s persistent queue turns a volatile in‑memory buffer into disk‑backed durability, how to configure it, what trade‑offs to expect, and how to monitor queue state with the built‑in API.
Configuring Persistent Queues in Logstash for Durable Event Processing
Enable Logstash persistent queues to protect in‑flight events across restarts, with step‑by‑step configuration, verification, and rollback guidance.
Logstash Persistent Queue: Architecture Note for Durable In-Flight Buffering
Architecture guide for Logstash Persistent Queue: how to implement durable buffering, monitor queue health, and identify when to move to an external broker like Kafka.
Keeping Logs Safe: Using Logstash Persistent Queues for At‑Least‑Once Delivery
Learn how Logstash persistent queues protect in‑flight events during restarts, with a concrete configuration example, verification steps, and trade‑offs to consider.
Persistent queue configuration change from memory to persisted in Logstash pipelines
Persistent queue behavior changes when a Logstash pipeline moves from the default in-memory queue to a persisted disk-backed queue. The documented change shifts memory pressure to disk, alters backpressure when queue.max_bytes is reached, and changes restart semantics to replay unacknowledged pages. Version assumptions matter because queue.type names and def