# Remote monitoring cluster, no ES data

**URL:** <https://discuss.elastic.co/t/remote-monitoring-cluster-no-es-data/130743>\
**Category:** Elasticsearch\
**Created:** [May 6, 2018, 12:20pm UTC](https://discuss.elastic.co/t/remote-monitoring-cluster-no-es-data/130743 "2018-05-06T12:20:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pjanzen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pjanzen/32/13756_2.png) [@pjanzen](https://discuss.elastic.co/u/pjanzen)\
**Post date:** [May 6, 2018, 12:20pm UTC](https://discuss.elastic.co/t/remote-monitoring-cluster-no-es-data/130743/1 "2018-05-06T12:20:54Z")

</div>

Hi All,

I have followed this guide: [monitoring-production](https://www.elastic.co/guide/en/x-pack/6.2/monitoring-production.html) to setup my elasticsearch / logstash / kibana monitoring and when I look on my monitor cluster trough kibana -\> monitoring I have an overview of elasticsearch, kibana and logstash. For logstash and kibana I see my remote nodes but for elasticsearch I don't see them.

I am using version 6.2.4 for all components.

The monitoring elasticsearch config looks like this.

> cluster.name: clog-monitoring  
> node.name: tb-clog-emon1.xxx.local  
> path.data: /opt/elasticdb/data  
> path.logs: /var/log/elasticsearch  
> bootstrap.memory\_lock: true  
> network.host: ['10.80.3.80', '127.0.0.1']  
> discovery.zen.master\_election.ignore\_non\_master\_pings: true  
> discovery.zen.ping.unicast.hosts: ["10.80.3.80","10.80.3.81","10.80.3.82","10.80.3.83","10.80.3.84"]  
> xpack.monitoring.enabled: true  
> xpack.security.enabled: false  
> xpack.monitoring.collection.indices: '_'  
> http.cors.enabled: true  
> http.cors.allow-origin: "/._/"  
> transport.tcp.compress: true  
> node.attr.box\_type: no\_data

My elasticsearch data nodes looks like this.

```
cluster.name: clog
node.name: tb-clog-esd1.tb.iss.local
path.data: /opt/elasticdb/data
path.logs: /var/log/elasticsearch
bootstrap.memory_lock: true
network.host: ['10.80.3.11', '127.0.0.1']
discovery.zen.master_election.ignore_non_master_pings: true
discovery.zen.ping.unicast.hosts: ["10.80.3.10","10.80.3.11","10.80.3.12","10.80.3.13","10.80.3.14","10.80.3.15","10.80.3.16","10.80.3.17","10.80.3.18","10.80.3.19","10.80.3.20","10.80.3.2
1","10.80.3.22","10.80.3.23","10.80.3.24","10.80.3.25","10.80.3.26","10.80.3.27","10.80.3.28","10.80.3.29","10.80.3.30","10.80.3.4","10.80.3.5","10.80.3.6","10.80.3.7","10.80.3.8","10.80.3
.9"]
xpack.security.enabled: false
node.master: false
node.data: true
node.ingest: true
xpack.monitoring.collection.indices: clog-*
xpack.monitoring.exporters:
  id1:
    type: http
    host: ['10.80.3.80','10.80.3.81','10.80.3.82','10.80.3.83','10.80.3.84']
gateway.recover_after_time: 2m
discovery.zen.minimum_master_nodes: 2
gateway.recover_after_nodes: 12
gateway.expected_data_nodes: 20
http.cors.enabled: true
http.cors.allow-origin: "/.*/"
transport.tcp.compress: true
node.attr.box_type: ssd

```

For completeness, this is how my logstash.yml is looking.

```
node.name: tb-clog-ls1
path.config: /etc/logstash/conf.d
path.data: /var/lib/logstash
path.logs: /opt/logstash/logs
#pipeline.workers: 20
#pipeline.output.workers: 20
http.host: 0.0.0.0
http.port: 9600-9700
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.url: ["http://10.80.3.80:9200", "http://10.80.3.81:9200", "http://10.80.3.82:9200", "http://10.80.3.83:9200", "http://10.80.3.84:9200"]
xpack.monitoring.elasticsearch.username: "elastic"
xpack.monitoring.elasticsearch.password: "changeme"

```

---

<div class="post-metadata">

**Author:** ![pjanzen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pjanzen/32/13756_2.png) [@pjanzen](https://discuss.elastic.co/u/pjanzen)\
**Post date:** [May 6, 2018, 1:50pm UTC](https://discuss.elastic.co/t/remote-monitoring-cluster-no-es-data/130743/2 "2018-05-06T13:50:41Z")

</div>

Ok, the config needs to be on all the nodes in your cluster, not just your data nodes.

Pushed config to all ES nodes and problem is solved.

---

<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:** [June 3, 2018, 1:50pm UTC](https://discuss.elastic.co/t/remote-monitoring-cluster-no-es-data/130743/3 "2018-06-03T13:50:44Z")

</div>

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