# Logstash multiple pipelines and event processing

**URL:** <https://discuss.elastic.co/t/logstash-multiple-pipelines-and-event-processing/153537>\
**Category:** Logstash\
**Created:** [October 23, 2018, 7:46am UTC](https://discuss.elastic.co/t/logstash-multiple-pipelines-and-event-processing/153537 "2018-10-23T07:46:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kernelpanic](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@kernelpanic](https://discuss.elastic.co/u/kernelpanic)\
**Post date:** [October 23, 2018, 7:46am UTC](https://discuss.elastic.co/t/logstash-multiple-pipelines-and-event-processing/153537/1 "2018-10-23T07:46:53Z")

</div>

Logstash version: 6.3.2

Hello, in order to process Netflow logs I installed Elastiflow which requires use of a different pipeline; the only changes I made was to comment out path.config in the logstash.yaml file and add the following to pipelines.yml:

```
 - pipeline.id: default
  path.config: "/usr/local/etc/logstash/logstash.conf"

- pipeline.id: elastiflow
  path.config: "/usr/local/etc/logstash/elastiflow/logstash/elastiflow/conf.d/*.conf"

```

I don't think this worked as looking at the logstash-plain.log file shows that it doesn't start the elastiflow pipeline, however my question concerns log collection; I'm collecting Windows event logs via winlogbeat which is usually something like 200,000 logs every 15 minutes when running with the main pipeline, but when I enable multiple pipelines that collection rate drops to around 28,000 logs every 15 minutes.

Can anyone tell me why this is happening?

---

<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 20, 2018, 7:46am UTC](https://discuss.elastic.co/t/logstash-multiple-pipelines-and-event-processing/153537/2 "2018-11-20T07:46:55Z")

</div>

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