# Logstash multiple pipelines going into same index

**URL:** https://discuss.elastic.co/t/logstash-multiple-pipelines-going-into-same-index/128066
**Category:** Logstash
**Created:** [April 15, 2018, 8:11am UTC](https://discuss.elastic.co/t/logstash-multiple-pipelines-going-into-same-index/128066 "2018-04-15T08:11:27Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [April 15, 2018, 12:22pm UTC](https://discuss.elastic.co/t/logstash-multiple-pipelines-going-into-same-index/128066/2 "2018-04-15T12:22:05Z")

</div>

Are you using pipelines.yml? If so please show it to us. If not, this would be expected. Configuration files are not self-contained. logstash concatentates all the configuration files from a directory, reads from all the inputs, puts the events through the filters in order, then sends the events to all of the outputs.

Reading [this](https://discuss.elastic.co/t/send-data-to-right-pipeline-from-two-csv-files/126700) thread or [this one](https://discuss.elastic.co/t/beats-received-on-port-11001-are-being-processed-by-port-11000-config/126603/4) might help you.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-multiple-pipelines-going-into-same-index/128066)._