# 200 pipelines in logstash causing scalability issues

**URL:** <https://discuss.elastic.co/t/200-pipelines-in-logstash-causing-scalability-issues/305999>\
**Category:** Logstash\
**Tags:** elastic-stack-monitoring\
**Created:** [May 31, 2022, 6:21am UTC](https://discuss.elastic.co/t/200-pipelines-in-logstash-causing-scalability-issues/305999 "2022-05-31T06:21:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jatin\_gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jatin_gupta/32/77600_2.png) [@jatin\_gupta](https://discuss.elastic.co/u/jatin_gupta)\
**Post date:** [May 31, 2022, 6:21am UTC](https://discuss.elastic.co/t/200-pipelines-in-logstash-causing-scalability-issues/305999/1 "2022-05-31T06:21:24Z")

</div>

Hey

I need a design suggestion.

We have 200 microservices and a 4 node logstash HA setup.  
Now each microservice has to send logs to a different index. Current setup I have is, for each microservice we have a different pipeline in logstash on a particular port, and that port is mentioned in filebeat for that service.

This has caused 200 pipelines to come up in logstash which is causing issues and highly unscalable.

---

<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:** [June 28, 2022, 6:22am UTC](https://discuss.elastic.co/t/200-pipelines-in-logstash-causing-scalability-issues/305999/2 "2022-06-28T06:22:19Z")

</div>

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