# Metricbeat counter logstash API

**URL:** <https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [December 11, 2016, 7:58pm UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650 "2016-12-11T19:58:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jo\_De\_Troy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jo_de_troy/32/59858_2.png) [@Jo\_De\_Troy](https://discuss.elastic.co/u/Jo_De_Troy)\
**Post date:** [December 11, 2016, 7:58pm UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650/1 "2016-12-11T19:58:10Z")

</div>

Hello,

I was wondering if metricbeat can pull in metrics from logstash instances which are available though the logstash API (e.g. node stats API) ? Or is there another way to get insight on the performance/throughput of logstash instances?

Thanks in advance,  
Jo

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 12, 2016, 1:57pm UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650/2 "2016-12-12T13:57:20Z")

</div>

There is currently no Logstash Module in Metricbeat. But Logstashbeat could be what you are looking for: [https://github.com/consulthys/logstashbeat](https://github.com/consulthys/logstashbeat)

---

<div class="post-metadata">

**Author:** ![Jo\_De\_Troy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jo_de_troy/32/59858_2.png) [@Jo\_De\_Troy](https://discuss.elastic.co/u/Jo_De_Troy)\
**Post date:** [December 13, 2016, 9:09am UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650/3 "2016-12-13T09:09:53Z")

</div>

Thx for the pointer.

I've tried it and was able to get in compiled.  
But after starting it up it crashed with the error below:

```
 ./logstashbeat -c ./logstashbeat.yml -e -d "*"

```

> 2016/12/13 09:02:46.440125 beat.go:267: INFO Home path: [/usr/local/go/src/github.com/consulthys/logstashbeat] Config path: [/usr/local/go/src/github.com/consulthys/logstashbeat] Data path: [/usr/local/go/src/github.com/consulthys/logstashbeat/data] Logs path: [/usr/local/go/src/github.com/consulthys/logstashbeat/logs]  
> 2016/12/13 09:02:46.440201 beat.go:177: INFO Setup Beat: logstashbeat; Version: 6.0.0-alpha1  
> 2016/12/13 09:02:46.440226 processor.go:43: DBG Processors:  
> 2016/12/13 09:02:46.440237 beat.go:183: DBG Initializing output plugins  
> 2016/12/13 09:02:46.440247 logp.go:219: INFO Metrics logging every 30s  
> 2016/12/13 09:02:46.440363 output.go:167: INFO Loading template enabled. Reading template file: /usr/local/go/src/github.com /consulthys/logstashbeat/etc/logstashbeat.template.json  
> 2016/12/13 09:02:46.440598 output.go:178: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/l ocal/go/src/github.com/consulthys/logstashbeat/logstashbeat.template-es2x.json  
> 2016/12/13 09:02:46.440788 client.go:120: INFO Elasticsearch url: [http://elastic:9200](http://elastic:9200)  
> 2016/12/13 09:02:46.440827 outputs.go:106: INFO Activated elasticsearch as output plugin.  
> 2016/12/13 09:02:46.440835 publish.go:234: DBG Create output worker  
> 2016/12/13 09:02:46.440894 publish.go:276: DBG No output is defined to store the topology. The server fields might not be f illed.  
> 2016/12/13 09:02:46.440917 publish.go:291: INFO Publisher name: [logstash.mgt.company.com](http://logstash.mgt.company.com)  
> 2016/12/13 09:02:46.441129 async.go:63: INFO Flush Interval set to: 1s  
> 2016/12/13 09:02:46.441139 async.go:64: INFO Max Bulk Size set to: 50  
> 2016/12/13 09:02:46.441147 async.go:72: DBG create bulk processing worker (interval=1s, bulk size=50)  
> 2016/12/13 09:02:46.441260 logstashbeat.go:87: DBG Init logstashbeat  
> 2016/12/13 09:02:46.441271 logstashbeat.go:88: DBG Period 10s  
> 2016/12/13 09:02:46.441280 logstashbeat.go:89: DBG Watch [[http://127.0.0.1:9600](http://127.0.0.1:9600)]  
> 2016/12/13 09:02:46.441288 logstashbeat.go:90: DBG Capture 3 hot threads  
> 2016/12/13 09:02:46.441294 logstashbeat.go:91: DBG JVM statistics true  
> 2016/12/13 09:02:46.441311 logstashbeat.go:92: DBG Process statistics true  
> 2016/12/13 09:02:46.441326 logstashbeat.go:93: DBG Pipeline statistics true  
> 2016/12/13 09:02:46.441434 beat.go:207: INFO logstashbeat start running.  
> 2016/12/13 09:02:46.441457 logstashbeat.go:99: INFO logstashbeat is running! Hit CTRL-C to stop it.  
> 2016/12/13 09:02:56.441682 logstashbeat.go:116: DBG Hot threads for url: [http://127.0.0.1:9600](http://127.0.0.1:9600)  
> 2016/12/13 09:02:57.126712 logstashbeat.go:122: DBG Hot threads detail: &{Host:logstash Version:5.0.2 Http\_ address:127.0.0.1:9600 Hot\_threads:{Time:2016-12-13T10:02:56+01:00 Busiest\_threads:3 Threads:[0xc42001adc0 0xc42001af80 0xc4 2001b140]}}  
> panic: runtime error: invalid memory address or nil pointer dereference  
> [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x46b5a2]

> goroutine 30 [running]:  
> panic(0x8a2920, 0xc4200120f0)  
> /usr/local/go/src/runtime/panic.go:500 +0x1a1  
> [github.com/consulthys/logstashbeat/beater.(\*Logstashbeat).Run.func1](http://github.com/consulthys/logstashbeat/beater.(*Logstashbeat).Run.func1)(0xc42015b380, 0xc42015b400)  
> /usr/local/go/src/github.com/consulthys/logstashbeat/beater/logstashbeat.go:131 +0x17d2  
> created by [github.com/consulthys/logstashbeat/beater.(\*Logstashbeat).Run](http://github.com/consulthys/logstashbeat/beater.(*Logstashbeat).Run)  
> /usr/local/go/src/github.com/consulthys/logstashbeat/beater/logstashbeat.go:211 +0x9d

Any idea if there are plans to incorporate the logstash metrics into a metricbeat module?

Best Regards,  
Jo

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 14, 2016, 8:29am UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650/4 "2016-12-14T08:29:26Z")

</div>

Best is to open a Github issue in logstashbeat so the problem can be fixed. There are no immediate plans to add a Logstash module. It is planned that Logstash can send its own metrics directly to elasticsearch.

---

<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:** [January 11, 2017, 8:29am UTC](https://discuss.elastic.co/t/metricbeat-counter-logstash-api/68650/5 "2017-01-11T08:29:30Z")

</div>

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