# Metricbeat data differs greatly from Elasticsearch Endpoint

**URL:** https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327
**Category:** Beats
**Tags:** metricbeat
**Created:** [February 21, 2020, 10:01am UTC](https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327 "2020-02-21T10:01:47Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Mattness](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattness/32/52975_2.png) [@Mattness](https://discuss.elastic.co/u/Mattness)
#### Post date: [February 21, 2020, 10:01am UTC](https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327/1 "2020-02-21T10:01:47Z")

</div>

So I wanted to build some dashboards with metric data about my elasticsearch instance.  
From the endpoint Get /nodes/\_stats I get all the data I need.

With the metricset "node\_stats" from the metricbeat module "elasticsearch" I get only a portion of this data. This is really frustrating since the stack monitoring dashboard (auto generated in kibana) seems to have access to this data via xpack monitoring.

Can I access this data any other way than via the endpoint?

---

<div class="post-metadata">

### Author: ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 25, 2020, 11:32am UTC](https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327/2 "2020-02-25T11:32:55Z")

</div>

Hi @Mattness 🙂

It will be nice if you can detail what's exactly missing? It might be a bug or simply a misunderstanding of what you are expecting.

The very first thing is that `_nodes/stats` endpoint is not being fetched by the `node_stats` metricset . The metricset uses `_nodes/_local/stats`. While `node` metricset fetches `/_nodes/_local`.

I don't know if what you are missing is the metrics from the rest of the nodes in a cluster. In such case, you should configure Metricbeat to point to each of them. This is the recommended way to work.

---

<div class="post-metadata">

### Author: ![Mattness](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattness/32/52975_2.png) [@Mattness](https://discuss.elastic.co/u/Mattness)
#### Post date: [February 27, 2020, 8:27am UTC](https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327/3 "2020-02-27T08:27:36Z")

</div>

Thanks for your answer. I compromised by using a HttpExporter to route the xpack monitoring data to an extra cluster. This contains all the data I wanted in the first place.

My production cluster was running in single-node mode. So there was only one node for metricbeat to monitor. I think the key difference - as you stated - was the one between the note\_stats and nodes/local/stats endpoints.

---

<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: [March 26, 2020, 8:27am UTC](https://discuss.elastic.co/t/metricbeat-data-differs-greatly-from-elasticsearch-endpoint/220327/4 "2020-03-26T08:27:53Z")

</div>

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