# Best way to manage a bunch of beats

**URL:** <https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830>\
**Category:** Beats\
**Created:** [April 8, 2016, 4:10pm UTC](https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830 "2016-04-08T16:10:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![szhem](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@szhem](https://discuss.elastic.co/u/szhem)\
**Post date:** [April 8, 2016, 4:10pm UTC](https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830/1 "2016-04-08T16:10:19Z")

</div>

Hi there!

Looking at the available beats

1. [https://www.elastic.co/products/beats](https://www.elastic.co/products/beats)
2. [https://www.elastic.co/guide/en/beats/libbeat/current/community-beats.html](https://www.elastic.co/guide/en/beats/libbeat/current/community-beats.html)

it seems that the trend is to create a single beat for every single piece of software.  
Don't you think that it looks to be quite difficult to manage a number of beats which also have to be monitored?  
What do you think regarding plugin-like approach and a single daemon?

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [April 8, 2016, 9:27pm UTC](https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830/2 "2016-04-08T21:27:58Z")

</div>

We're definitely aware that we cannot expect people to run 20 Beats :-). We currently have an effort to group some of the Beats that have very similar functionality (poll an API then capture metrics) into a single Metricbeat. So we expect that for most people, running Filebeat and Metricbeat will be enough.

We also plan to offer all the elastic Beats into a single binary form, but we're only in the design phase for that.  
The reason we didn't do it so far is that Go doesn't have a good way of handling plugins.

---

<div class="post-metadata">

**Author:** ![szhem](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@szhem](https://discuss.elastic.co/u/szhem)\
**Post date:** [April 19, 2016, 9:44am UTC](https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830/3 "2016-04-19T09:44:23Z")

</div>

Hi @tudor!

Thanks a lot for clarification.  
Does it make sense to look at how [mozilla's heka](https://github.com/mozilla-services/heka/tree/be1420d226808485a557ad622bb75785cadfa43a/sandbox/lua) implements plugin-like mechanism by means of lua?

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [April 19, 2016, 9:47am UTC](https://discuss.elastic.co/t/best-way-to-manage-a-bunch-of-beats/46830/4 "2016-04-19T09:47:01Z")

</div>

That's interesting, thanks for the link, I'll check it.

---

<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/best-way-to-manage-a-bunch-of-beats/46830/5 "2017-07-05T21:53:02Z")

</div>


