Persistent Queue storage buffers telemetry data temporarily, preventing data loss when destinations are unavailable or during collector maintenance.
Badger Persistent Queue – Not Recommended
Badger is designed to use available system memory for filesystem caching. While this behavior is expected and does not negatively impact system performance, it can make agents appear to consume more memory than anticipated and harder to monitor. To reduce potential confusion around reported memory usage, consider switching to Pebble or Bolt.
Bolt is currently the default persistent queue storage backend, but this may change in the future.
Bindplane supports three persistent queue backends that write to local disk when destinations cannot keep up, each comes with its own benefits and drawbacks.
Pebble is the recommended storage backend for most Bindplane deployments. It provides excellent performance with minimal configuration.
Use Pebble for:
Balanced disk I/O
Medium to high throughput workloads
Smaller disk footprints for your telemetry
See Pebble for configuration options.
Bolt is the original persistent queue backend and remains fully supported for the short term. However, Pebble offers in most cases better performance for persistent queueing.
Use Bolt for:
Existing deployments already using it successfully
See Bolt for more information and upgrade guidance.
Are you having performance issues?
Lock contention errors in logs: Upgrade from Bolt to Pebble
Queue not draining: Upgrade from Bolt to Pebble
Review your current deployment
Select the appropriate persistent queue for your desired outcome
Ensure to follow the Configuration guide in order to not lose data during the transition
Monitor performance and resource usage
For detailed configuration information:
Last updated
Was this helpful?
Was this helpful?
