# Filebeat Logstash scaling

**URL:** <https://discuss.elastic.co/t/filebeat-logstash-scaling/108872>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 23, 2017, 11:26am UTC](https://discuss.elastic.co/t/filebeat-logstash-scaling/108872 "2017-11-23T11:26:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntviet18](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ntviet18/32/24565_2.png) [@ntviet18](https://discuss.elastic.co/u/ntviet18)\
**Post date:** [November 23, 2017, 11:26am UTC](https://discuss.elastic.co/t/filebeat-logstash-scaling/108872/1 "2017-11-23T11:26:50Z")

</div>

I have a BELK cluster in Kubernetes. Recently I need to scale number of my Logstash instances. However, Filebeats just keep pushing logs to the older instances. How long will it take for Filebeats to detects the new instances?

---

<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:** [November 23, 2017, 8:27pm UTC](https://discuss.elastic.co/t/filebeat-logstash-scaling/108872/2 "2017-11-23T20:27:40Z")

</div>

@ntviet18 Currently Filebeat autodiscovery is only for module or prospector, it wont update the outputs configuration. Usually people get around that by one of the following:

- Use a tool like ansible or puppets to update FB configuration
- Use a queue like kafka
- Use a proxy to hide the logstash behind it.

Thanks

---

<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:** [December 21, 2017, 8:28pm UTC](https://discuss.elastic.co/t/filebeat-logstash-scaling/108872/3 "2017-12-21T20:28:39Z")

</div>

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