# Monitoring cluster
**URL:** https://discuss.elastic.co/t/monitoring-cluster/199222
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [September 12, 2019, 9:57am UTC](https://discuss.elastic.co/t/monitoring-cluster/199222 "2019-09-12T09:57:14Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@akshay\_singh2](https://discuss.elastic.co/u/akshay_singh2)
#### Post date: [September 12, 2019, 9:57am UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/1 "2019-09-12T09:57:14Z")
Hello Team,
I have deployed elastic monitoring cluster for my production cluster, now I can see monitoring data to new cluster, but cant see the same data in production cluster monitoring tab of kibana.
Is this normal, I can see below message in Kibana for monitoring in prod cluster.
```
## You need to make some adjustments
To run monitoring please perform the following steps
We checked the `cluster defaults` settings for `xpack.monitoring.exporters` , and found the reason: `Remote exporters indicate a possible misconfiguration: id1` .
Using monitoring exporters ship the monitoring data to a remote monitoring cluster is highly recommended as it keeps the integrity of the monitoring data safe no matter what the state of the production cluster. However, as this instance of Kibana could not find any monitoring data, there seems to be a problem with the `xpack.monitoring.exporters` configuration, or the `xpack.monitoring.elasticsearch` settings in `kibana.yml` .
Check that the intended exporters are enabled for sending statistics to the monitoring cluster, and that the monitoring cluster host matches the `xpack.monitoring.elasticsearch` setting in `kibana.yml` to see monitoring data in this instance of Kibana.
```
Production ES configuration:
```
xpack.monitoring.history.duration=7d
xpack.monitoring.exporters.id1.type=http
xpack.monitoring.exporters.id1.host=http://monitoring_cluster_ip:9500
xpack.monitoring.elasticsearch.collection.enabled=true
xpack.monitoring.collection.indices=.monitoring* (Can I change this for all indecies, what will be the impact and benifites)
xpack.monitoring.collection.enabled=true
node.name=${HOSTNAME}
node.master=true
node.data=false
indices.memory.index_buffer_size=40%
http.cors.enabled=true
http.cors.allow-origin=*
discovery.zen.ping.unicast.hosts=es-master
discovery.zen.minimum_master_nodes=2
cluster.routing.allocation.awareness.attributes=rack_id
cluster.name=prodcution-es
```
Monitoring cluster config:
```
xpack.security.enabled=false
xpack.monitoring.collection.enabled=false
node.name=${HOSTNAME}
node.master=true
node.ingest=true
node.data=true
http.port=9500
http.cors.enabled=true
http.cors.allow-origin=*
discovery.zen.ping.unicast.hosts=es-monitoring-cluster
discovery.zen.minimum_master_nodes=2
cluster.name=es-monitoring
```
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [September 12, 2019, 1:43pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/2 "2019-09-12T13:43:08Z")
Hi @akshay_singh2,
> now I can see monitoring data to new cluster,
Just to clarify, you mean you are seeing `.monitoring-*` indices on the _monitoring_ cluster?
Can you also share your `kibana.yml` for the _production_ cluster? You'll need to set `xpack.monitoring.elasticsearch.hosts` so Kibana knows to look there for the monitoring data (without setting that, it will just look at the _production_ cluster instead). [See this document for more information](https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html).
Also, this is tangential, but the `xpack.monitoring.history.duration=7d` setting will _only work_ if you are using a `local` exporter. [See this document for more information](https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-settings.html)
---
### Author:  [@akshay\_singh2](https://discuss.elastic.co/u/akshay_singh2)
#### Post date: [September 16, 2019, 9:23am UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/3 "2019-09-16T09:23:24Z")
> [@chrisronline](#):
>
> Can you also share your `kibana.yml` for the _production_ cluster?
Here is my kibana.yml for production cluster:
```
server.host: '0.0.0.0'
server.name: "Kibana(PAD)"
elasticsearch.url: 'http://10.95.122.113:9200/'
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.hosts: 'http://10.95.122.113:9200/'
xpack.monitoring.ui.container.elasticsearch.enabled: true
xpack.monitoring.kibana.collection.enabled: true
```
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [September 16, 2019, 1:26pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/4 "2019-09-16T13:26:28Z")
Can you share your cluster settings for _both_ the _production_ and _monitoring_ cluster?
---
### Author:  [@akshay\_singh2](https://discuss.elastic.co/u/akshay_singh2)
#### Post date: [September 17, 2019, 4:56pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/5 "2019-09-17T16:56:56Z")
Cluster setting of ?
Kibana or elasticsearch?
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [September 17, 2019, 5:07pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/6 "2019-09-17T17:07:46Z")
Cluster settings for Elasticsearch, both clusters please.
[https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-get-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-get-settings.html)
---
### Author:  [@akshay\_singh2](https://discuss.elastic.co/u/akshay_singh2)
#### Post date: [September 17, 2019, 5:23pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/7 "2019-09-17T17:23:23Z")
> [@akshay\_singh2](#):
>
> Production ES configuration:
>
> ```auto
> xpack.monitoring.history.duration=7d
> xpack.monitoring.exporters.id1.type=http
> xpack.monitoring.exporters.id1.host=http://monitoring_cluster_ip:9500
> xpack.monitoring.elasticsearch.collection.enabled=true
> xpack.monitoring.collection.indices=.monitoring* (Can I change this for all indecies, what will be the impact and benifites)
> xpack.monitoring.collection.enabled=true
> node.name=${HOSTNAME}
> node.master=true
> node.data=false
> indices.memory.index_buffer_size=40%
> http.cors.enabled=true
> http.cors.allow-origin=*
> discovery.zen.ping.unicast.hosts=es-master
> discovery.zen.minimum_master_nodes=2
> cluster.routing.allocation.awareness.attributes=rack_id
> cluster.name=prodcution-es
>
> ```
>
> Monitoring cluster config:
>
> ```auto
> xpack.security.enabled=false
> xpack.monitoring.collection.enabled=false
> node.name=${HOSTNAME}
> node.master=true
> node.ingest=true
> node.data=true
> http.port=9500
> http.cors.enabled=true
> http.cors.allow-origin=*
> discovery.zen.ping.unicast.hosts=es-monitoring-cluster
> discovery.zen.minimum_master_nodes=2
> cluster.name=es-monitoring
>
> ```
It's been there in the opening of thread.
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [September 17, 2019, 5:39pm UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/8 "2019-09-17T17:39:16Z")
That is the config file. Cluster settings are retrieved from an ES API. Please see -\> [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-get-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-get-settings.html)
---
### Author:  [@akshay\_singh2](https://discuss.elastic.co/u/akshay_singh2)
#### Post date: [September 18, 2019, 6:09am UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/9 "2019-09-18T06:09:56Z")
There is nothing pretty much in cluster setting for both clusters:
```
{
"persistent" : { },
"transient" : { }
}
```
Its same for both cluster.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 16, 2019, 6:09am UTC](https://discuss.elastic.co/t/monitoring-cluster/199222/10 "2019-10-16T06:09:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.