# Logstash via kafka - case for pipeline usage?

**URL:** <https://discuss.elastic.co/t/logstash-via-kafka-case-for-pipeline-usage/174637>\
**Category:** Logstash\
**Created:** [March 30, 2019, 1:08pm UTC](https://discuss.elastic.co/t/logstash-via-kafka-case-for-pipeline-usage/174637 "2019-03-30T13:08:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [March 30, 2019, 1:08pm UTC](https://discuss.elastic.co/t/logstash-via-kafka-case-for-pipeline-usage/174637/1 "2019-03-30T13:08:19Z")

</div>

Loading metric/file beat data via 2 kafka queues. Consumer are configured to eacI have a single 'filter' file with 20-30 index choices determined via if/then/else if. Could I get better performance if I split this up to a pipeline / index? Am I even thinking about pipelines correctly?

Situation: significant kafka lag on a new clustered installation. Am getting ~15K events / second but data nodes are not working very hard. Am wondering if logstash filter processing could be a bottleneck.

---

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [March 30, 2019, 3:24pm UTC](https://discuss.elastic.co/t/logstash-via-kafka-case-for-pipeline-usage/174637/2 "2019-03-30T15:24:12Z")

</div>

Hmm.. upon further reading Im thinking to be stuck with 1 pipeline since all this work shares a common input: 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:** [April 27, 2019, 3:24pm UTC](https://discuss.elastic.co/t/logstash-via-kafka-case-for-pipeline-usage/174637/3 "2019-04-27T15:24:14Z")

</div>

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