# Multiple logstash-instances on 1 elasticsearch-cluster **URL:** \ **Category:** Logstash\ **Created:** [August 6, 2015, 6:43pm UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002 "2015-08-06T18:43:34Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jarmoni](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jarmoni](https://discuss.elastic.co/u/jarmoni)\ **Post date:** [August 6, 2015, 6:43pm UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/1 "2015-08-06T18:43:34Z")
We are developing a distributed, docker-based server-application. We run several docker-containers on each host. The idea is to put a logstash-instance (as a docker-container) on each host which publishes to a single elasticsearch-cluster. A kibana frontend should sit on top ot the elasticsearch cluster. Since I am new to logstash and elasticsearch, I have some questions: 1.) Is this setup possible? 2.) Is this setup "good practice"? 3.) Can I monitor my logs on the kibana-frontend in the same way as if I use a single logstash instance or do I have to partition the database in some way? Thanks in advance for any reply. ---
**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:** [August 7, 2015, 10:47am UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/2 "2015-08-07T10:47:05Z")
1. Yes 2. It's sane, if it works for you then go for it! 3. Can you elaborate more? ---
**Author:** ![jarmoni](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jarmoni](https://discuss.elastic.co/u/jarmoni)\ **Post date:** [August 7, 2015, 7:00pm UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/3 "2015-08-07T19:00:07Z")
We want to keep the setup as simple as possible - with HA and scaling in mind. Our scenario is: 1. Each processing-host runs the same services (containers) - these services are stateless, if one host fails: Never mind. The next request will be routed to another instance. 2. There are database-hosts which are (of course) not stateless - but scale well (Cassandra, Elasticsearch) 3. So in my opinion we have 2 choices: To use a central logstash-instance (and make it high-available) or deploy one instance per host. The 2nd approach seems much more simple to me: 1. If the host goes down, logstash is dead too (on this host) but it would not make any differency if I ran it on a different machine: Result: No logs from this server. 2. We don't have to deal with HA-issues. ---
**Author:** ![jarmoni](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jarmoni](https://discuss.elastic.co/u/jarmoni)\ **Post date:** [August 7, 2015, 7:22pm UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/4 "2015-08-07T19:22:44Z")
If logstash itself could bring the machine down this would be of course a problem.... ---
**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:** [August 7, 2015, 10:57pm UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/5 "2015-08-07T22:57:38Z")
Ahh ok. They yes that makes sense. LS won't bring down a machine 🙂 ---
**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:32am UTC](https://discuss.elastic.co/t/multiple-logstash-instances-on-1-elasticsearch-cluster/27002/6 "2017-07-06T05:32:34Z")