# Launching a multi-file logstash config

**URL:** <https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344>\
**Category:** Logstash\
**Created:** [June 29, 2016, 11:42pm UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344 "2016-06-29T23:42:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![3ygun](https://avatars.discourse-cdn.com/v4/letter/3/67e7ee/32.png) [@3ygun](https://discuss.elastic.co/u/3ygun)\
**Post date:** [June 29, 2016, 11:42pm UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/1 "2016-06-29T23:42:55Z")

</div>

I have a multi-file configuration however when launching it I with `-f` I get different outputs from:

- `bin/logstash -f PATH_TO_CONFIG_DIR/`  
and
- `bin/logstash -f PATH_TO_CONFIG_DIR/*.conf`

I was under the impression these should give the same output as long as the destination directory only contains `.conf` files. However, my trials say otherwise \>\> The 4th run with `.conf` doesn't test the configuration:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/4/4adba94e98562728a1590a907c95f7d088b33bb6.PNG)

Notes:

- `...-logstash/conf/` does only contain `.conf` files
- and the `...-logstash/conf/` directory is inside `.../logstash-2.3.3/bin/`

---

<div class="post-metadata">

**Author:** ![noemie](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@noemie](https://discuss.elastic.co/u/noemie)\
**Post date:** [June 30, 2016, 11:39am UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/2 "2016-06-30T11:39:34Z")

</div>

Hello.

So you'd like to know why the 4th one does not have the same output tha the other commands?

---

<div class="post-metadata">

**Author:** ![3ygun](https://avatars.discourse-cdn.com/v4/letter/3/67e7ee/32.png) [@3ygun](https://discuss.elastic.co/u/3ygun)\
**Post date:** [June 30, 2016, 2:23pm UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/3 "2016-06-30T14:23:43Z")

</div>

Yes.

---

<div class="post-metadata">

**Author:** ![noemie](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@noemie](https://discuss.elastic.co/u/noemie)\
**Post date:** [June 30, 2016, 2:25pm UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/4 "2016-06-30T14:25:49Z")

</div>

I'll only be able to suppose why but I think it's due to the -w flag. Specifying the number of workers might induce the launching of Logstash

---

<div class="post-metadata">

**Author:** ![3ygun](https://avatars.discourse-cdn.com/v4/letter/3/67e7ee/32.png) [@3ygun](https://discuss.elastic.co/u/3ygun)\
**Post date:** [June 30, 2016, 9:05pm UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/5 "2016-06-30T21:05:24Z")

</div>

Adding or removing the `-w 1` for a single work does nothing to change the behavior:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/9/9f47808d09bd28b9717bdc79c931f115d6a544d0.PNG)

This GitHub issue implies that either way should work:

- [Load Config Parsing](https://github.com/elastic/logstash/issues/1831)

---

<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:** [July 6, 2017, 4:50am UTC](https://discuss.elastic.co/t/launching-a-multi-file-logstash-config/54344/6 "2017-07-06T04:50:02Z")

</div>

Closed on July 6, 2017, 4:50am UTC


