ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Filebeat Autodiscover lets Beats automatically detect and ship logs from new containers, eliminating manual config. Learn how to set up Docker providers, write matching templates, test, and avoid common pitfalls.
Beats already flush and persist state on SIGTERM via close(); the real design work is grace periods, the disk queue, and knowing exactly what SIGKILL costs you.
Learn how to add Lua processors to Filebeat for custom transformations while monitoring resource impact.
Learn how the Elastic Beats architecture uses libbeat, backpressure handling, and optimizing resource usage on edge hosts.
Goal Determine the most cost‑effective queue strategy for Elastic Beats when the monitored traffic is minimal. Constraints Beats provide two documented queue implementations: In‑memory queue – low CPU and disk I/O, but loses buffered events on crash. Persistent disk queue – writes events to local storage before shipping, adding durability at the expense of h
beats
docker