# Central Management and Docker

**URL:** <https://discuss.elastic.co/t/central-management-and-docker/162654>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 2, 2019, 12:54pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654 "2019-01-02T12:54:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rasmus\_Fredensborg\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rasmus_fredensborg_j/32/39354_2.png) [@Rasmus\_Fredensborg\_J](https://discuss.elastic.co/u/Rasmus_Fredensborg_J)\
**Post date:** [January 2, 2019, 12:54pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654/1 "2019-01-02T12:54:20Z")

</div>

Hi,  
Thank you for your amazing products. I'm trying to use Central Management to configure filebeats that run in their own Docker containers. The problem is that the filebeat containers may restart, and when this happens, the filebeat is registered as a new beat in Central Management. I would like to know if there is a way to have "unique" beats in Central Management, so that if a filebeat with a given name or tag attempts to register again, it is not registered as a new beat.

Thanks again

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [January 2, 2019, 2:14pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654/2 "2019-01-02T14:14:01Z")

</div>

@Rasmus_Fredensborg_J Thanks for looking at Central Management! Today we do not have this option, but we plan to have the enroll subcommand to support specifying the tag [https://github.com/elastic/beats/issues/9596](https://github.com/elastic/beats/issues/9596)

Since you are using Docker did you take a look at the [autodiscover docker](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover.html), this might be more appropriate for your use case?

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [January 2, 2019, 2:20pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654/3 "2019-01-02T14:20:18Z")

</div>

After talking with the team, my solution would work in your case, but what you actually want is support for ephemeral client, we are planning to support that use case for APM but we do not have a clear plan for it yet.

---

<div class="post-metadata">

**Author:** ![Rasmus\_Fredensborg\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rasmus_fredensborg_j/32/39354_2.png) [@Rasmus\_Fredensborg\_J](https://discuss.elastic.co/u/Rasmus_Fredensborg_J)\
**Post date:** [January 2, 2019, 2:27pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654/4 "2019-01-02T14:27:16Z")

</div>

Thank you for your very quick response, @pierhugues! I will look into the autodiscover docker configuration 😃

---

<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:** [January 30, 2019, 2:27pm UTC](https://discuss.elastic.co/t/central-management-and-docker/162654/5 "2019-01-30T14:27:24Z")

</div>

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