# Elasticsearch is multiplying data per \*.conf I have

**URL:** <https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383>\
**Category:** Elasticsearch\
**Created:** [September 6, 2019, 9:22am UTC](https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383 "2019-09-06T09:22:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![HikariNTB](https://avatars.discourse-cdn.com/v4/letter/h/bb73d2/32.png) [@HikariNTB](https://discuss.elastic.co/u/HikariNTB)\
**Post date:** [September 6, 2019, 9:22am UTC](https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383/1 "2019-09-06T09:22:23Z")

</div>

Hi,

I'm setting my ELK system and I need to input 3 different `*.conf` as to input the data from my logs. The problem is that for some reason, when I reboot Logstash, the logs goes to Elasticsearch correctly but it shows data (at Kibana) as many times as indexes with that grok on it.

As I explain myself so bad, I add this screenshot to show you what I see:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/e/5ebc4db629027ef8aa7fbca06f6b4bb38e3dc8f1.png)

My `*.conf` configuration are this 4 times just changing directions and `ilm*` names:

> input {  
> file {  
> path =\> "/home/admin/environments/tests/test03/\*"  
> sincedb\_path =\> "/dev/null"  
> mode =\> "read"  
> ignore\_older =\> "10 d"  
> file\_completed\_action =\> "delete"  
> }  
> }
> 
> filter {  
> grok {  
> match =\> { "message" =\> "^%{DATA:prex}###############hidden\_data##############$"}  
> }  
> if ("\_grokparsefailure" in [tags]) {  
> drop{}  
> }  
> }
> 
> output {  
> elasticsearch {  
> hosts =\> ["127.0.0.1:9200"]  
> ilm\_rollover\_alias =\> "test3"  
> ilm\_pattern =\> "000001"  
> ilm\_policy =\> "test3"  
> }  
> stdout { codec =\> rubydebug }  
> }

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 7, 2019, 10:34am UTC](https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383/2 "2019-09-07T10:34:04Z")

</div>

When you store multiple configuration files in the config directory these are not treated as separate pipelines but concatenated into a single one. This means that all inputs gets processed by all filters and sent to all outputs unless you use conditionals to control the flow.

---

<div class="post-metadata">

**Author:** ![HikariNTB](https://avatars.discourse-cdn.com/v4/letter/h/bb73d2/32.png) [@HikariNTB](https://discuss.elastic.co/u/HikariNTB)\
**Post date:** [September 9, 2019, 8:56am UTC](https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383/3 "2019-09-09T08:56:16Z")

</div>

Now it works perfectly!

Thank you so much.

Hope this issue can be helpful for others 🙂

(New configuration of pipeline now have no "`*`", instead it contains the hole "`.conf`" route)

---

<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:** [October 7, 2019, 8:56am UTC](https://discuss.elastic.co/t/elasticsearch-is-multiplying-data-per-conf-i-have/198383/4 "2019-10-07T08:56:18Z")

</div>

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