# How to use Logstash monitoring API?
**URL:** https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658
**Category:** Logstash
**Created:** [February 2, 2017, 11:04am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658 "2017-02-02T11:04:37Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 2, 2017, 11:04am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/1 "2017-02-02T11:04:37Z")
Hi,
I have multiple Logstash instances and it will be fine if I can see their status in a Kibana dashboard. I got to know about Logstash monitoring API here [https://www.elastic.co/guide/en/logstash/current/monitoring.html](https://www.elastic.co/guide/en/logstash/current/monitoring.html) but I dont know how to use it / how to work with it. I entered `GET /_node/pipeline` in Kibana Dev Tools \> Console, but it returned;
```
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "No endpoint or operation is available at [pipeline]"
}
],
"type": "illegal_argument_exception",
"reason": "No endpoint or operation is available at [pipeline]"
},
"status": 400
}
```
How can I monitor Logstash instances (whether they are up or not), and display it in a Kibana dashboard?
Thank you.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 2, 2017, 11:11am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/2 "2017-02-02T11:11:54Z")
With the release of Elastic Stack 5.2, X-Pack Monitoring now supports [monitoring Logstash](https://www.elastic.co/guide/en/x-pack/current/monitoring-logstash.html) as well as Elasticsearch and Kibana. This is available through the free [Basic X-Pack license](https://www.elastic.co/subscriptions).
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 2, 2017, 11:15am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/3 "2017-02-02T11:15:06Z")
Ok..
@Christian_Dahlqvist Will this show my each Logstash instance separately, or a combined one?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 2, 2017, 8:34pm UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/4 "2017-02-02T20:34:41Z")
I believe there are separate screens for overview and instance level information.
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 3, 2017, 4:47am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/5 "2017-02-03T04:47:26Z")
Ok.
Could you tell me if this is possible without X-Pack? I got to know that Logstash has a monitoring API [https://www.elastic.co/guide/en/logstash/5.0/monitoring.html](https://www.elastic.co/guide/en/logstash/5.0/monitoring.html) but I don't know how to use it 😔 could you help me with it?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 3, 2017, 6:25am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/6 "2017-02-03T06:25:02Z")
The monitoring data is available through an HTTP end-point described in the documentation, so if you have something poll this at a regular interval, perform any transformation that is required and index it into Elasticsearch, you should be able to build Kibana dashboards around it. I have however not used the API, so will not really be able to help with the details. Is there any reason you can not use X-Pack with the free basic license?
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 3, 2017, 6:29am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/7 "2017-02-03T06:29:44Z")
@Christian_Dahlqvist I am using X-Pack with basic license, but its GA 5.0.0.
When I tried `GET /_node/pipeline` in Kibana console, it returned no end point error. Is it possible to use this with GA 5.0.0?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 3, 2017, 6:33am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/8 "2017-02-03T06:33:55Z")
Monitoring of Logstash in X-Pack was introduced in version 5.2. There has been a number of bug fixes and enhancements since 5.0, so I would recommend you upgrade.
The Kibana console queries the Elasticsearch cluster only for security reasons, so you can not use Console to query the HTTP end point on Logstash.
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 3, 2017, 6:39am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/9 "2017-02-03T06:39:06Z")
Ok @Christian_Dahlqvist .. I can upgrade, but takes time I think.
I have entered `curl -XGET "http://localhost:9200/_node/pipeline"` in my Linux console, but it returned;
```
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"No endpoint or operation is available at [pipeline]"}],"type":"illegal_argument_exception","reason":"No endpoint or operation is available at [pipeline]"},"status":400}
```
Why is this happening?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 3, 2017, 6:56am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/10 "2017-02-03T06:56:35Z")
The API is available on the Logstash process, not Elasticsearch, and therefore uses port 9600 by default, not 9200.
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [February 3, 2017, 7:39am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/11 "2017-02-03T07:39:05Z")
Thank you so much @Christian_Dahlqvist 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 3, 2017, 7:39am UTC](https://discuss.elastic.co/t/how-to-use-logstash-monitoring-api/73658/12 "2017-03-03T07:39:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.