# Getting logs from several servers

**URL:** <https://discuss.elastic.co/t/getting-logs-from-several-servers/1513>\
**Category:** Logstash\
**Created:** [May 28, 2015, 8:08pm UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513 "2015-05-28T20:08:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![psampson](https://avatars.discourse-cdn.com/v4/letter/p/22d042/32.png) [@psampson](https://discuss.elastic.co/u/psampson)\
**Post date:** [May 28, 2015, 8:08pm UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513/1 "2015-05-28T20:08:34Z")

</div>

Hi,  
I currently have logstash-forwarder running on about 8 servers sending their logs to one logstash instance. I'd like to add this to about a hundred more and I was wondering if it makes sense to have the servers use a shared directory and simply have logstash run off that directory instead of putting logstash or logstash-forwarder on all of them.

My concern with putting logstash on each server is maintaining and updating it across all servers, as I am still fairly new using it and it is likely that changes and updates will be made to it in the near future.

Are there any downsides to using a shared directory or is there a better solution that I am missing?

Thanks!

---

<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:** [May 29, 2015, 2:24am UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513/2 "2015-05-29T02:24:40Z")

</div>

This is why using config management, Puppet/Ansible/Chef, makes sense.  
Having a single shared logging directory makes some sense, but may not really scale at that level.

You should really be looking to use a broker as well.

---

<div class="post-metadata">

**Author:** ![psampson](https://avatars.discourse-cdn.com/v4/letter/p/22d042/32.png) [@psampson](https://discuss.elastic.co/u/psampson)\
**Post date:** [May 29, 2015, 5:15pm UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513/3 "2015-05-29T17:15:00Z")

</div>

Thanks a lot. I figured there would probably be a better way. Can you suggest some brokers as well?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [May 30, 2015, 3:07pm UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513/4 "2015-05-30T15:07:35Z")

</div>

Well, just have a look at what input plugins Logstash supports. That's a major limiting factor anyway. Popular choices include Redis, RabbitMQ, and Kafka.

---

<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, 5:39am UTC](https://discuss.elastic.co/t/getting-logs-from-several-servers/1513/5 "2017-07-06T05:39:01Z")

</div>


