# Collectd monitoring of ElasticSearch with CURL\_JSON plugin failing

**URL:** <https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920>\
**Category:** Elasticsearch\
**Created:** [August 5, 2015, 7:54pm UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920 "2015-08-05T19:54:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [August 5, 2015, 7:54pm UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920/1 "2015-08-05T19:54:09Z")

</div>

In our environment, we're using Collectd 4.10.1 (I know ... old as dirt, but its a requirement of RightScale) and we are trying to leverage the curl\_json plugin to pull metrics from our ElasticSearch cluster. We have the metrics coming in properly from [http://localhost:9200/\_cluster/stats](http://localhost:9200/_cluster/stats) and [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health).

What we can't get working though are _any_ metrics from [http://localhost:9200/\_nodes/\_local/stats](http://localhost:9200/_nodes/_local/stats). No matter how many or few metrics I define, and no matter whether I use 'nodes/\*/...' or 'nodes//...', I cannot seem to get any data from this endpoint.

Here is our entire collectd elasticsearch.conf file, and a real copy of the raw node stats json output:  
[https://gist.github.com/diranged/ac7d2edb45b0eba00d42](https://gist.github.com/diranged/ac7d2edb45b0eba00d42)

Any ideas on what might be going on? I can't seem to get any debug logs either, and unfortunately the collectd-dbg package for 4.10.1 is not available it seems like, so we're really hamstrung here.

I have verified that ..

- Collectd is indeed making the curl call to ElasticSearch and the response is coming back properly (via strace, and tcpdump)
- Replacing '\*' with 'HYUqTMnfSgmvd87\_o3UPLw' (the node id) in the config file does not help
- Dropping all the way down to a single metric (jvm/mem/heap\_used\_in\_bytes) does not help

Can anyone help here?

---

<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:** [August 7, 2015, 3:59am UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920/2 "2015-08-07T03:59:06Z")

</div>

What version of ES are you on?

---

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [August 7, 2015, 3:37pm UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920/3 "2015-08-07T15:37:16Z")

</div>

We're running 1.5.2 right now.

---

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [December 8, 2015, 8:22pm UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920/4 "2015-12-08T20:22:20Z")

</div>

Hey .. we're still stuck on this issue. I've tried everything I can think of to fix it, and we cannot figure out whats happening. We're upgraded to ElasticSearch 1.7.1 now. I've narrowed down the data being returned to this:

```auto
{
    "cluster_name": "nsp-es-staging-us1",
    "nodes": {
        "zDQZnKxxQPC1uOe7qZYHcA": {
            "timestamp": 1449605835281,
            "name": "staging-us1-es-access-uswest2-5-i-bd52dd64-nsp-es-staging-us1",
            "transport_address": "inet[/10.32.17.234:9300]",
            "host": "xxx,
            "ip": [
                "inet[/10.32.17.234:9300]",
                "NONE"
            ],
            "attributes": {
                "aws_availability_zone": "us-west-2a",
                "data": "false",
                "master": "true"
            },
            "http": {
                "current_open": 8,
                "total_opened": 114
            }
        }
    }
}

```

and set up a simple collectd config:

```auto
LoadPlugin curl_json
<Plugin curl_json>
  <URL "http://127.0.0.1:9200/_nodes/_local/stats/http?pretty=true">
    Instance "elasticsearch"
    <Key "nodes/zDQZnKxxQPC1uOe7qZYHcA/http/current_open">
      Type "gauge"
      Instance "http_current_open"
    </Key>
  </URL>
</Plugin>

```

Yet, its still not working.. anyone else run into anything like this?

---

<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 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/collectd-monitoring-of-elasticsearch-with-curl-json-plugin-failing/26920/5 "2017-07-05T23:32:29Z")

</div>