Monitoring cluster

Elastic Stack Elasticsearch
1

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
2

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.

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

3

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
4

Can you share your cluster settings for both the production and monitoring cluster?

5

Cluster setting of ?
Kibana or elasticsearch?

6

Cluster settings for Elasticsearch, both clusters please.

https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-get-settings.html

7

It's been there in the opening of thread.

8

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

9

There is nothing pretty much in cluster setting for both clusters:

{
  "persistent" : { },
  "transient" : { }
}

Its same for both cluster.

10

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