Kibana monitoring - (wrong) data from remote cluster

[kluvi (Jakub Kluvánek)]

@shaunak

Which versions of ES and Kibana are you running?

cluster 2 is 6.5.4
cluster 1 is 6.4.1 (we will update it today also to 6.5.4)

@shaunak

Can you provide a screenshot of the Monitoring UI on Kibana 2?

(URL is https://XXXXXXX/app/monitoring#/overview?_g=(ccs:reglendo-es-cluster,cluster_uuid:'8EpTnISFS8qg03qU1YxWUw') where XXXXXXX is domain of kibana 2)

@shaunak

Can you provide your kibana.yml for kibana 1 and kibana 2, after masking any sensitive information?

We run Kibana in docker container (image docker.elastic.co/kibana/kibana:6.5.4 without any custom modifications) and set only environment variables SERVER_NAME and ELASTICSEARCH_URL

@shaunak

For each cluster, can your provide the results of this query: GET _cluster/settings?include_defaults&filter_path=*.xpack.monitoring.*

cluster 1:

cluster 2:

I see, that on cluster 2, there is xpack.monitoring.collection.enabled: false, but its weird, because its only in defaults section... Why is it different on each cluster?

btw I updated the settings through PUT /_cluster/settings and ES creates the .monitoring-* index and now I can see correct cluster in Monitoring in Kibana.

So thank you for your hints