# Reliability of Filebeat

**URL:** <https://discuss.elastic.co/t/reliability-of-filebeat/47627>\
**Category:** Beats\
**Created:** [April 18, 2016, 9:13am UTC](https://discuss.elastic.co/t/reliability-of-filebeat/47627 "2016-04-18T09:13:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gringo](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@gringo](https://discuss.elastic.co/u/gringo)\
**Post date:** [April 18, 2016, 9:13am UTC](https://discuss.elastic.co/t/reliability-of-filebeat/47627/1 "2016-04-18T09:13:35Z")

</div>

Is there any documents on the reliability of Filebeat? How does it ensure the reliability of the delivery of the logs. E.g. In packet loss situation, Elasticsearch is down, avoid duplication?

Does Filebeat have some kind of Queue system in it?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [April 18, 2016, 11:46am UTC](https://discuss.elastic.co/t/reliability-of-filebeat/47627/2 "2016-04-18T11:46:31Z")

</div>

See [Recovery mechanism in filebeat](https://discuss.elastic.co/t/recovery-mechanism-in-filebeat/47539)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 9:53pm UTC](https://discuss.elastic.co/t/reliability-of-filebeat/47627/3 "2017-07-05T21:53:08Z")

</div>