# Logs are ignoring input section in config files

**URL:** https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480
**Category:** Logstash
**Created:** [March 25, 2018, 11:13am UTC](https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480 "2018-03-25T11:13:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![arliber](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@arliber](https://discuss.elastic.co/u/arliber)
#### Post date: [March 25, 2018, 11:13am UTC](https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480/1 "2018-03-25T11:13:51Z")

</div>

Hi,

I have a simple setup for capturing logs though HTTP and TCP. I've created 2 conf files at /etc/logstash/conf.d/ (see below) but logs sent though HTTP are also being passed through the TCP pipeline and vise versa. For example when I send a log through TCP it ends up both in http-logger-\* index and in tcp-logger-\*.. it makes no sense to me ☹

**http\_logger.conf**

```
input {
  http {
    port => 9884
  }
}
filter {
    grok {
      match => ["[headers][request_path]", "\/(?<component>[\w-]*)(?:\/)?(?<env>[\w-]*)(?:\/)?"]
    }
}
output {
    amazon_es {
        hosts => ['XXXXX']
        region => 'us-west-2'
        aws_access_key_id => 'XXXXX'
        aws_secret_access_key => 'XXXXX'
        index => 'http-logger-%{+YYYY.MM.dd}'
    }
    stdout { codec => rubydebug }
}

```

**tcp\_logger.conf**

```
input {
  tcp {
    port => 9885
    codec => json
  }
}
filter {

}
output {
    amazon_es {
        hosts => ['XXXXX']
        region => 'us-west-2'
        aws_access_key_id => 'XXXXX'
        aws_secret_access_key => 'XXXXX'
        index => 'tcp-logger-%{+YYYY.MM.dd}'
    }
    stdout { codec => rubydebug }
}

```

Any ideas on what am I missing? Thank you

---

<div class="post-metadata">

### Author: ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [March 25, 2018, 2:02pm UTC](https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480/2 "2018-03-25T14:02:31Z")

</div>

Originally, each Logstash process only had one pipeline. Since pipelines could get pretty complex, users were able to break their configurations up into multiple files, which would be reassembled into a single pipeline when Logstash started up.

Then, [Multiple Pipelines](https://www.elastic.co/guide/en/logstash/current/multiple-pipelines.html) were introduced; you'll need to use `pipelines.yml` to opt into the multi-pipeline experience.

---

<div class="post-metadata">

### Author: ![arliber](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@arliber](https://discuss.elastic.co/u/arliber)
#### Post date: [March 26, 2018, 4:13pm UTC](https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480/3 "2018-03-26T16:13:50Z")

</div>

That works perfectly, thank you!

---

<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 23, 2018, 4:13pm UTC](https://discuss.elastic.co/t/logs-are-ignoring-input-section-in-config-files/125480/4 "2018-04-23T16:13:58Z")

</div>

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