# Elasticsearch output split problem

**URL:** <https://discuss.elastic.co/t/elasticsearch-output-split-problem/153268>\
**Category:** Elasticsearch\
**Created:** [October 21, 2018, 3:36am UTC](https://discuss.elastic.co/t/elasticsearch-output-split-problem/153268 "2018-10-21T03:36:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![abu.sayeed](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@abu.sayeed](https://discuss.elastic.co/u/abu.sayeed)\
**Post date:** [October 21, 2018, 3:36am UTC](https://discuss.elastic.co/t/elasticsearch-output-split-problem/153268/1 "2018-10-21T03:36:39Z")

</div>

I have some custom grok in logstash conf.d directory. That grok split /home/local/example/example.log path data. I wish - /var/log/\*.log path data will be split via filebeat system module and /home/local/example/example.log path data will be split via custom grok.

If I configue filebeat.yum like

output.logstash:  
hosts: ["192.168.10.1:5044"]

/home/local/example/example.log path data split field:  
"Class" =\> "c.n.s.s.SmsGatewayService:331"  
"source" =\> "/home/local/example/example.log",  
"@timestamp" =\> 2018-10-03T09:35:57.404Z,  
"Thread" =\> "http-nio-8080-exec-6",  
"host" =\> {  
"name" =\> "vm1"  
},

But I configure filebeat like

setup.kibana:  
host: "192.168.10.1:5601"

output.elasticsearch:  
hosts: ["192.168.10.1:9200"]

/home/local/example/example.log path data will not be split:  
message:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.

I need to split module data and custom path data via output elasticsearch and kibana host.

Thanks for help me

---

<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:** [November 18, 2018, 3:36am UTC](https://discuss.elastic.co/t/elasticsearch-output-split-problem/153268/2 "2018-11-18T03:36:42Z")

</div>

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