If you're running metricbeat on a laptop, or on a remote host with spotty network connectivity, you may have periods where you cannot reach your ES cluster to upload stats. This means you lose the stats over these periods of disconnect, which may actually prove to be useful.
In these sorts of instances it'd be great if we could still collect stats, store them locally, then upload them upon reconnection to the endpoint cluster.
I'm imagining some kind of compressed file that we store somewhere after a configurable period of time, then slowly stream to ES.
markwalkom
All 6 comments
@markwalkom We are discussing a potential local queue on the beats side for some time which would help in these cases. The change will probably happen in libbeat so it is available to all beats.
ruflin
on 9 Dec 2016
+1
DirkAmelinckx
on 8 Aug 2017
+1
loekvangool
on 3 Oct 2017
+1
devKlausS
on 9 Feb 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![botelastic[bot] picture](https://avatars0.githubusercontent.com/u/6764390?v=4&s=40)
botelastic[bot]
on 9 Jul 2020
This issue doesn't have a Team:<team> label.
botelastic[bot]
on 9 Jul 2020
Related issues
nicpenning
路
3Comments
musayev-io
路
3Comments
feelan03
路
3Comments
jsoriano
路
3Comments
exekias
路
3Comments
Most helpful comment
@markwalkom We are discussing a potential local queue on the beats side for some time which would help in these cases. The change will probably happen in libbeat so it is available to all beats.