# Cross cluster Monitoring **URL:** \ **Category:** Elasticsearch\ **Created:** [July 11, 2017, 9:19am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611 "2017-07-11T09:19:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![abraxxa](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@abraxxa](https://discuss.elastic.co/u/abraxxa)\ **Post date:** [July 11, 2017, 9:19am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/1 "2017-07-11T09:19:40Z")
I'm trying to find out if Kibana 5.5 supports accessing monitoring data of remove clusters using the cross cluster search feature. We have a central three-node Elasticsearch cluster and plan to scale by adding per customer custer which can be searched centrally using a cross cluster gateway node (is that the correct name?) on the server running Kibana. Since Kibana 5.5 this works but the X-Pack monitoring data from Logstash and Elasticsearch itself logged to the central ES cluster isn't displayed in Kibana. ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [July 17, 2017, 8:01pm UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/2 "2017-07-17T20:01:56Z")
Hi Alexander, We've had some preliminary discussions about using Cross Cluster Search for Monitoring. But it's not currently supported or recommended. For now, you should set up a dedicated monitoring cluster and have all your clustered forward their data to it. And then configure the monitoring cluster in the kibana.yml. Thanks, Lee ---
**Author:** ![abraxxa](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@abraxxa](https://discuss.elastic.co/u/abraxxa)\ **Post date:** [July 18, 2017, 5:49am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/3 "2017-07-18T05:49:37Z")
Hi Lee, thanks for your response! So the central Kibana can't display the data from the monitoring cluster? Do I need to install a separate Kibana for the monitoring cluster? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 18, 2017, 5:52am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/4 "2017-07-18T05:52:50Z")
Yes that is correct. ---
**Author:** ![abraxxa](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@abraxxa](https://discuss.elastic.co/u/abraxxa)\ **Post date:** [July 18, 2017, 6:20am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/5 "2017-07-18T06:20:03Z")
Is support for cross cluster monitoring in Kibana on the roadmap? ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [July 18, 2017, 3:39pm UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/6 "2017-07-18T15:39:31Z")
You can set `xpack.monitoring.elasticsearch.url` in your kibana.yml to point to your monitoring cluster if it's not the same as where you want to store your .kibana index. xpack.monitoring.elasticsearch.url The location of the Elasticsearch instance(s) where your monitoring data is stored. By default, this is the same as the elasticsearch.url. This setting enables you to use a single Kibana instance to search and visualize data in your production cluster as well as monitor data sent to a dedicated monitoring cluster. [https://www.elastic.co/guide/en/kibana/5.5/monitoring-settings-kb.html](https://www.elastic.co/guide/en/kibana/5.5/monitoring-settings-kb.html) ---
**Author:** ![abraxxa](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@abraxxa](https://discuss.elastic.co/u/abraxxa)\ **Post date:** [July 19, 2017, 7:23am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/7 "2017-07-19T07:23:00Z")
Excellent! Configured and works! I was focusing on cross-cluster search when searching in the docs so missed that config option. I guess when I configure the coordinating Elasticsearch node to store its monitoring data in another ES cluster I can disable the following settings as I've initially intended: ``` node.master: false # required because only node in cluster node.data: false # required for kibana to store it's dashboards node.ingest: false # required for x-pack monitoring ``` The Elasticsearch docs where lacking in this area when I setup the coordinating ES node for cross-cluster search. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 16, 2017, 7:23am UTC](https://discuss.elastic.co/t/cross-cluster-monitoring/92611/8 "2017-08-16T07:23:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.