# Multiple Databases and Indexes Logstash

**URL:** <https://discuss.elastic.co/t/multiple-databases-and-indexes-logstash/204129>\
**Category:** Logstash\
**Created:** [October 17, 2019, 8:56pm UTC](https://discuss.elastic.co/t/multiple-databases-and-indexes-logstash/204129 "2019-10-17T20:56:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gucarletto](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@gucarletto](https://discuss.elastic.co/u/gucarletto)\
**Post date:** [October 17, 2019, 8:56pm UTC](https://discuss.elastic.co/t/multiple-databases-and-indexes-logstash/204129/1 "2019-10-17T20:56:49Z")

</div>

I am using Logstash to sync 4 tables from Mysql to Elasticsearch. My problem is how to scale this to 200 hundred customers. Each customer is in a different database schema and possibly other server too. Every customer should be in a different index on Elastic. What would be the best approach? Should I run logstash in every server and sync all databases from it with the four pipelines getting the results from multiple jdbc inputs and multiple indexes outputs? Or should I configure it with docker and kubernetes so each docker instance handle one input and output?

---

<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:** [November 14, 2019, 8:56pm UTC](https://discuss.elastic.co/t/multiple-databases-and-indexes-logstash/204129/2 "2019-11-14T20:56:52Z")

</div>

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