# Bulk handling of logstash conf files

**URL:** <https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803>\
**Category:** Logstash\
**Created:** [June 15, 2016, 4:31am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803 "2016-06-15T04:31:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 15, 2016, 4:31am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/1 "2016-06-15T04:31:18Z")

</div>

I have like 10 clients using logstash to send data to a central ES server, however, everytime when I have some modification to the conf files, I needed to modify each clients logstash conf files. That could be so time consuming. Are there any ways I can have a distributor come with elasticsearch that can help do the work and distribute the files?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 15, 2016, 4:40am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/2 "2016-06-15T04:40:45Z")

</div>

Are you not using automated deployments; Puppet, ansible, chef, salt etc?

Future versions of LS will use an inbuilt, distributed config management, something like storing it in an ES index.

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 15, 2016, 5:02am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/3 "2016-06-15T05:02:42Z")

</div>

Yes, I had tried using ansible thereafter but just would like to know if there are any functionality provided by ES or logstash in doing similar things.  
Thanks for your information, I am anyway great looking forward to using the distributed config management

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 27, 2016, 4:38am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/4 "2016-06-27T04:38:21Z")

</div>

Which version of logstash will be available for having this configuration management?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 27, 2016, 8:36pm UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/5 "2016-06-27T20:36:16Z")

</div>

Not sure, it's on our roadmap, but we don't provide timings for features.

---

<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 6, 2017, 4:50am UTC](https://discuss.elastic.co/t/bulk-handling-of-logstash-conf-files/52803/6 "2017-07-06T04:50:46Z")

</div>