# Can someone explain Beats Architecture?

**URL:** <https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [October 25, 2017, 1:21pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249 "2017-10-25T13:21:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmpsoares](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cmpsoares/32/16608_2.png) [@cmpsoares](https://discuss.elastic.co/u/cmpsoares)\
**Post date:** [October 25, 2017, 1:21pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249/1 "2017-10-25T13:21:55Z")

</div>

Hello,

We're analysing the Beats for custom beat developments, and I was wondering if someone can explain the architecture under the hood?

I remember to see a diagram of it (from an old version) but was not able to find it anymore and imagine it changed significantly.

Thank you very much.

Best regards,  
Carlos SOARES.

---

<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:** [October 25, 2017, 1:46pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249/2 "2017-10-25T13:46:03Z")

</div>

For 5.x releases have a [look at this talk](https://www.elastic.co/elasticon/conf/2017/sf/ship-your-own-data-tailoring-beats-to-your-use-case).

---

<div class="post-metadata">

**Author:** ![cmpsoares](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cmpsoares/32/16608_2.png) [@cmpsoares](https://discuss.elastic.co/u/cmpsoares)\
**Post date:** [October 26, 2017, 4:44pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249/3 "2017-10-26T16:44:27Z")

</div>

Hello,

Thank you very much!  
Are there already some resources available for version 6.X?

Best regards,  
Carlos SOARES.

---

<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:** [October 27, 2017, 1:03pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249/4 "2017-10-27T13:03:27Z")

</div>

No resources for 6.0 yet. Architecture is mostly the same (libbeat diagram is pretty high level 😉 ). Some common functionality has been moved to libbeat + output interfaces have been updated/simplified (somewhat internal API).

- filebeat removes spooler + publisher workers (filebeat publishing has become async, making use of spooling/buffering in libbeat itself) -\> libbeat notifies the registrar
- winlogbeat 6.0 uses async publishing pipeline -\> libbeat notifies registrar
- no 'big' changes in metricbeat/haertbeat. Auditbeat uses metricbeat as framework
- packetbeat no real change (I think `flows publisher` worker has been removed)

---

<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:** [November 24, 2017, 1:03pm UTC](https://discuss.elastic.co/t/can-someone-explain-beats-architecture/105249/5 "2017-11-24T13:03:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.