# Logtsash output to ElasticSearch Cluster

**URL:** https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983
**Category:** Elasticsearch
**Created:** [September 26, 2014, 6:28pm UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983 "2014-09-26T18:28:02Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Kevin\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_m/32/69498_2.png) [@Kevin\_M](https://discuss.elastic.co/u/Kevin_M)
#### Post date: [September 26, 2014, 6:28pm UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/1 "2014-09-26T18:28:02Z")

</div>

Do i need to set anything up special to have logstash output to my  
elasticsearch cluster?

output {  
stdout { }  
elasticsearch {  
cluster =\> "es-cluster"  
}  
}

I have my logstash output setup this way but I do not get anything in  
kibana - when I switch to elasticsearch\_http it works fine and data shows up

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 27, 2014, 8:34am UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/2 "2014-09-27T08:34:15Z")

</div>

Is the cluster external to the LS instance?  
Check the logs of your ES master server, it should show the logstash node  
join, if you aren't seeing that then enable verbose mode in LS and you  
should see the issue.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 27 September 2014 04:28, Kevin M [mcgkev29@gmail.com](mailto:mcgkev29@gmail.com) wrote:

> Do i need to set anything up special to have logstash output to my  
> elasticsearch cluster?
> 
> output {  
> stdout { }  
> elasticsearch {  
> cluster =\> "es-cluster"  
> }  
> }
> 
> I have my logstash output setup this way but I do not get anything in  
> kibana - when I switch to elasticsearch\_http it works fine and data shows up
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Z1TSCWq%2BvbfMP%2BZCnOSPzPvdX7yY7RxqXbiz5PNZ%2Bb4g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Z1TSCWq%2BvbfMP%2BZCnOSPzPvdX7yY7RxqXbiz5PNZ%2Bb4g%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Kevin\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_m/32/69498_2.png) [@Kevin\_M](https://discuss.elastic.co/u/Kevin_M)
#### Post date: [September 29, 2014, 12:33pm UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/3 "2014-09-29T12:33:19Z")

</div>

so it is setup as

Server1  
Logstash ES Kibana  
server 2  
ES only

When I go to the elasticHQ website I see the 2 nodes joined up and healthy

I will check Logstash thanks

On Saturday, September 27, 2014 4:34:45 AM UTC-4, Mark Walkom wrote:

> Is the cluster external to the LS instance?  
> Check the logs of your ES master server, it should show the logstash node  
> join, if you aren't seeing that then enable verbose mode in LS and you  
> should see the issue.
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \<javascript:\>  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 27 September 2014 04:28, Kevin M \<[mcgk...@gmail.com](mailto:mcgk...@gmail.com) \<javascript:\>\>  
> wrote:
> 
> > Do i need to set anything up special to have logstash output to my  
> > elasticsearch cluster?
> > 
> > output {  
> > stdout { }  
> > elasticsearch {  
> > cluster =\> "es-cluster"  
> > }  
> > }
> > 
> > I have my logstash output setup this way but I do not get anything in  
> > kibana - when I switch to elasticsearch\_http it works fine and data shows up
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/55c1549d-b115-4257-ab67-8219c3c965c9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/55c1549d-b115-4257-ab67-8219c3c965c9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Kevin\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_m/32/69498_2.png) [@Kevin\_M](https://discuss.elastic.co/u/Kevin_M)
#### Post date: [September 29, 2014, 12:40pm UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/4 "2014-09-29T12:40:32Z")

</div>

So here is the really, i think, relevant log message I got:

log4j, [2014-09-29T08:35:22.061] WARN: org.elasticsearch.discovery:  
[Asmodeus] waited for 30s and no initial state was set by the discovery

then a bit later:

log4j, [2014-09-29T08:35:22.061] WARN: org.elasticsearch.discovery:  
[Asmodeus] waited for 30s and no initial state was set by the discovery

log4j, [2014-09-29T08:36:27.385] WARN:  
org.elasticsearch.discovery.zen.ping.multicast: [Asmodeus] failed to  
read requesting data from  
/172.16.40.29:54328  
java.io.IOException: Expected handle header, got [13]  
at  
org.elasticsearch.common.io.stream.HandlesStreamInput.readString(HandlesStreamInput.java:65)  
at  
org.elasticsearch.cluster.ClusterName.readFrom(ClusterName.java:64)  
at  
org.elasticsearch.cluster.ClusterName.readClusterName(ClusterName.java:58)  
at  
org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:409  
)  
at java.lang.Thread.run(Thread.java:745)  
log4j, [2014-09-29T08:36:28.895] WARN:  
org.elasticsearch.discovery.zen.ping.multicast: [Asmodeus] failed to  
read requesting data from  
/172.16.40.29:54328  
java.io.IOException: Expected handle header, got [13]  
at  
org.elasticsearch.common.io.stream.HandlesStreamInput.readString(HandlesStreamInput.java:65)  
at  
org.elasticsearch.cluster.ClusterName.readFrom(ClusterName.java:64)  
at  
org.elasticsearch.cluster.ClusterName.readClusterName(ClusterName.java:58)  
at  
org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:409  
)  
at java.lang.Thread.run(Thread.java:745)

{:timestamp=\>"2014-09-29T08:36:23.583000-0400", :message=\>"Failed to flush  
outgoing items", :outgoing\_count=\>51,  
:exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
waited for [30s],  
:backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
"org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
"java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
{:timestamp=\>"2014-09-29T08:36:54.632000-0400", :message=\>"Failed to flush  
outgoing items", :outgoing\_count=\>51,  
:exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
waited for [30s],  
:backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
"org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
"java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
{:timestamp=\>"2014-09-29T08:37:25.673000-0400", :message=\>"Failed to flush  
outgoing items", :outgoing\_count=\>51,  
:exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
waited for [30s],  
:backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
"org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
"java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
{:timestamp=\>"2014-09-29T08:37:56.735000-0400", :message=\>"Failed to flush  
outgoing items", :outgoing\_count=\>51,  
:exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
waited for [30s],  
:backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
"org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
"java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}

Thanks,  
Kevin

On Saturday, September 27, 2014 4:34:45 AM UTC-4, Mark Walkom wrote:

> Is the cluster external to the LS instance?  
> Check the logs of your ES master server, it should show the logstash node  
> join, if you aren't seeing that then enable verbose mode in LS and you  
> should see the issue.
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \<javascript:\>  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 27 September 2014 04:28, Kevin M \<[mcgk...@gmail.com](mailto:mcgk...@gmail.com) \<javascript:\>\>  
> wrote:
> 
> > Do i need to set anything up special to have logstash output to my  
> > elasticsearch cluster?
> > 
> > output {  
> > stdout { }  
> > elasticsearch {  
> > cluster =\> "es-cluster"  
> > }  
> > }
> > 
> > I have my logstash output setup this way but I do not get anything in  
> > kibana - when I switch to elasticsearch\_http it works fine and data shows up
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e2353e6e-bb64-4f60-bc63-fc5a3d7a6ac3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e2353e6e-bb64-4f60-bc63-fc5a3d7a6ac3%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Kevin\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_m/32/69498_2.png) [@Kevin\_M](https://discuss.elastic.co/u/Kevin_M)
#### Post date: [September 29, 2014, 1:44pm UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/5 "2014-09-29T13:44:23Z")

</div>

Think i may have fixed it by upgrading to Logstash 1.4.2

On Monday, September 29, 2014 8:40:32 AM UTC-4, Kevin M wrote:

> So here is the really, i think, relevant log message I got:
> 
> log4j, [2014-09-29T08:35:22.061] WARN: org.elasticsearch.discovery:  
> [Asmodeus] waited for 30s and no initial state was set by the discovery
> 
> then a bit later:
> 
> log4j, [2014-09-29T08:35:22.061] WARN: org.elasticsearch.discovery:  
> [Asmodeus] waited for 30s and no initial state was set by the discovery
> 
> log4j, [2014-09-29T08:36:27.385] WARN:  
> org.elasticsearch.discovery.zen.ping.multicast: [Asmodeus] failed to  
> read requesting data from /  
> 172.16.40.29:54328  
> java.io.IOException: Expected handle header, got [13]  
> at  
> org.elasticsearch.common.io.stream.HandlesStreamInput.readString(HandlesStreamInput.java:65)  
> at  
> org.elasticsearch.cluster.ClusterName.readFrom(ClusterName.java:64)  
> at  
> org.elasticsearch.cluster.ClusterName.readClusterName(ClusterName.java:58)  
> at  
> org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:409  
> )  
> at java.lang.Thread.run(Thread.java:745)  
> log4j, [2014-09-29T08:36:28.895] WARN:  
> org.elasticsearch.discovery.zen.ping.multicast: [Asmodeus] failed to  
> read requesting data from /  
> 172.16.40.29:54328  
> java.io.IOException: Expected handle header, got [13]  
> at  
> org.elasticsearch.common.io.stream.HandlesStreamInput.readString(HandlesStreamInput.java:65)  
> at  
> org.elasticsearch.cluster.ClusterName.readFrom(ClusterName.java:64)  
> at  
> org.elasticsearch.cluster.ClusterName.readClusterName(ClusterName.java:58)  
> at  
> org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:409  
> )  
> at java.lang.Thread.run(Thread.java:745)
> 
> {:timestamp=\>"2014-09-29T08:36:23.583000-0400", :message=\>"Failed to flush  
> outgoing items", :outgoing\_count=\>51,  
> :exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
> waited for [30s],  
> :backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
> "org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
> "java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
> {:timestamp=\>"2014-09-29T08:36:54.632000-0400", :message=\>"Failed to flush  
> outgoing items", :outgoing\_count=\>51,  
> :exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
> waited for [30s],  
> :backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
> "org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
> "java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
> {:timestamp=\>"2014-09-29T08:37:25.673000-0400", :message=\>"Failed to flush  
> outgoing items", :outgoing\_count=\>51,  
> :exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
> waited for [30s],  
> :backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
> "org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
> "java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}  
> {:timestamp=\>"2014-09-29T08:37:56.735000-0400", :message=\>"Failed to flush  
> outgoing items", :outgoing\_count=\>51,  
> :exception=\>org.elasticsearch.discovery.MasterNotDiscoveredException:  
> waited for [30s],  
> :backtrace=\>["org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:180)",  
> "org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:483)",  
> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)",  
> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)",  
> "java.lang.Thread.run(Thread.java:745)"], :level=\>:warn}
> 
> Thanks,  
> Kevin
> 
> On Saturday, September 27, 2014 4:34:45 AM UTC-4, Mark Walkom wrote:
> 
> > Is the cluster external to the LS instance?  
> > Check the logs of your ES master server, it should show the logstash node  
> > join, if you aren't seeing that then enable verbose mode in LS and you  
> > should see the issue.
> > 
> > Regards,  
> > Mark Walkom
> > 
> > Infrastructure Engineer  
> > Campaign Monitor  
> > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com)  
> > web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> > 
> > On 27 September 2014 04:28, Kevin M [mcgk...@gmail.com](mailto:mcgk...@gmail.com) wrote:
> > 
> > > Do i need to set anything up special to have logstash output to my  
> > > elasticsearch cluster?
> > > 
> > > output {  
> > > stdout { }  
> > > elasticsearch {  
> > > cluster =\> "es-cluster"  
> > > }  
> > > }
> > > 
> > > I have my logstash output setup this way but I do not get anything in  
> > > kibana - when I switch to elasticsearch\_http it works fine and data shows up
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1a4094e7-2457-4790-9a0e-5cec5bb7b12c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/32e7d5dc-210f-4c53-a5af-254b11ea93fb%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/32e7d5dc-210f-4c53-a5af-254b11ea93fb%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:59am UTC](https://discuss.elastic.co/t/logtsash-output-to-elasticsearch-cluster/19983/6 "2017-07-06T00:59:20Z")

</div>


