# Point Kibana 'Dev Tools' to remote ES cluster

**URL:** <https://discuss.elastic.co/t/point-kibana-dev-tools-to-remote-es-cluster/100768>\
**Category:** Kibana\
**Created:** [September 16, 2017, 3:36pm UTC](https://discuss.elastic.co/t/point-kibana-dev-tools-to-remote-es-cluster/100768 "2017-09-16T15:36:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [September 18, 2017, 7:09pm UTC](https://discuss.elastic.co/t/point-kibana-dev-tools-to-remote-es-cluster/100768/2 "2017-09-18T19:09:08Z")

</div>

I'm pretty sure you could use Cross Cluster Search. See the docs below. You would configure the monitoring cluster to give access to the compute cluster. Then in the Dev Tools Console you would use an index pattern that includes the remote cluster name like `compute:my_index`

[https://www.elastic.co/guide/en/elasticsearch/reference/5.5/modules-cross-cluster-search.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/modules-cross-cluster-search.html)

Let me know if you need help with it.

Regards,  
Lee

---

_[View the full topic](https://discuss.elastic.co/t/point-kibana-dev-tools-to-remote-es-cluster/100768)._
