# Multiple pipelines in one logstash and kafka **URL:** \ **Category:** Logstash\ **Created:** [March 5, 2018, 12:36pm UTC](https://discuss.elastic.co/t/multiple-pipelines-in-one-logstash-and-kafka/122507 "2018-03-05T12:36:47Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\ **Post date:** [March 5, 2018, 12:36pm UTC](https://discuss.elastic.co/t/multiple-pipelines-in-one-logstash-and-kafka/122507/1 "2018-03-05T12:36:47Z")
Hi, currently we are using following chain: logfile -\> filebeat -\> logstash -\> elasticsearch. Sometimes I see in our logs, that filebeat cannot connect or is rejected by logstash. Thats why I am considering introducing kafka in our stack, so that we have following chain: logfile -\> filebeat -\> kafka -\> logstash -\> elasticsearch. We have about 25-30 logfile types represented by a field "logType". They need completely different parsing. Currently we are using conditionals and only the main pipeline. When configuring kafka output in filebeat I see the option to set the logType field as topic. For logstash I am thinking of setting one pipeline for a topic. So I also can drop the conditionals to check which logfiles are to process. Is it the right / a common approach / practice to do so? Are there any pitfalls? Do I need to expect any issues when a single logstash is processing about 30 kafka topics? (currently we use a single instance) Thanks a lot, Andreas ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 2, 2018, 12:37pm UTC](https://discuss.elastic.co/t/multiple-pipelines-in-one-logstash-and-kafka/122507/2 "2018-04-02T12:37:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.