# Issues & questions about --path.config usage

**URL:** <https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184>\
**Category:** Logstash\
**Created:** [August 6, 2018, 2:46pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184 "2018-08-06T14:46:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![somelifeDev](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@somelifeDev](https://discuss.elastic.co/u/somelifeDev)\
**Post date:** [August 6, 2018, 2:46pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/1 "2018-08-06T14:46:02Z")

</div>

Greeting,

To avoid having one big .conf receiving logs from filebeat on 5044, filtering through tons of ifs and elses, then forwarding to elastic, I've been trying to use the --path.config command lately as I understand it, it should append multiple .conf files together in a lexi~ order.  
The goal is the to make one .conf file per, say, application with just an "if [app][name] == "bla" and be done.

\*\*my .service relevant bit is \*\*  
`ExecStart=/usr/share/logstash/bin/logstash "--path.config" "/etc/logstash/config.d"`

**my folder structure is**  
/etc  
--/logstash  
----/conf.d  
------/\_input.conf  
------/app01.conf  
------/app02.conf  
------/app03.conf  
------/output.conf

\_input.conf contains the input, output the output  
The appXX.conf contains the filters.

I just can't get that logic to work...

---

<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:** [August 6, 2018, 2:49pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/2 "2018-08-06T14:49:31Z")

</div>

Your structure shows conf.d. Your command line has config.d. They need to match.

---

<div class="post-metadata">

**Author:** ![somelifeDev](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@somelifeDev](https://discuss.elastic.co/u/somelifeDev)\
**Post date:** [August 6, 2018, 2:53pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/3 "2018-08-06T14:53:07Z")

</div>

cheers.  
But the logic is sound? It should append all .conf files into one and treat it as one single pipeline?

---

<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:** [August 6, 2018, 2:54pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/4 "2018-08-06T14:54:01Z")

</div>

Yes.

---

<div class="post-metadata">

**Author:** ![somelifeDev](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@somelifeDev](https://discuss.elastic.co/u/somelifeDev)\
**Post date:** [August 6, 2018, 3:11pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/5 "2018-08-06T15:11:56Z")

</div>

Works like a charm, cheers!

---

<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:** [September 3, 2018, 3:11pm UTC](https://discuss.elastic.co/t/issues-questions-about-path-config-usage/143184/6 "2018-09-03T15:11:58Z")

</div>

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