currently I am using metricbeat with file output. Then filebeat is fetching the log and delivering to redis.
I know that metricbeat has redis output capability like filebeat.
So I would like to understand what happens to the system, events, resources if I use redis output directly in metricbeat.
If redis is available, I do not expect any issues.
But what happen, if the output is down?
If logging to file I expect filebeat just tailing a few lines and stop reading if backend is unreachable, so not much pressure on the system. Metricbeat is writing to rotating files. Only if backend is too long down I may loose data.
But what happens with metricbeat and the event generation, if backend is down and metricbeat is configured to push do backend directly?
- How many events will be stored?
- Will they be stored in memory or in on disk?
- Will they get lost on metricbeat restart?
- If stored on memory, is there a limit or can the host run out of memory because of metricbeat?
- If there is some limit (memory, event count, etc.) and it gets reached. Will it handle like a ring buffer and oldest events / blocks of events will be overwritten or will metricbeat just stop generating or even crash?
Thanks a lot,