# How Can I use Kibana to see indices in another ES Cluster?

**URL:** https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306
**Category:** Kibana
**Created:** [October 5, 2016, 6:59pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306 "2016-10-05T18:59:14Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 6:59pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/1 "2016-10-05T18:59:14Z")

</div>

I am trying to see data from a totally different ES Cluster set up by others. How Could see them in Kibana?

Shall I change the **elasticsearch.url** in the kibana.yml file and fill it with the new Cluster's server address?

Should I also change the IP and Host in **elasticsearch.yml**?

---

<div class="post-metadata">

### Author: ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [October 5, 2016, 9:36pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/2 "2016-10-05T21:36:54Z")

</div>

`elasticsearch.url` should include the host, port, and protocol, e.g. `http://localhost:9200`

Note however that you won't be able to see any of your existing index patterns or saved objects when you switch clusters. All of that information is stored in the cluster Kibana is pointing to.

---

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 9:48pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/3 "2016-10-05T21:48:51Z")

</div>

Below is the new cluster's address i want to connect to, should i have elasticsearch.url as **inet[ip-192-168-0-194.eu-west-1.compute.internal/192.168.0.194:9300]**?

"cluster\_name":"elasticsearch-stock-aws","nodes":{"MDJh1n6tQbqNTXOBbhVFow":{"name":"aws-elasticsearch-3"," **transport\_address**":"inet[ip-192-168-0-194.eu-west-1.compute.internal/192.168.0.194:9300]","host":"ip-192-168-0-194","ip":"192.168.0.194","version":"1.7.5","build":"00f95f4","http\_address":"inet[/192.168.0.194:8080]","attributes":{"master":"true"},"settings":{"cluster":{"name":"elasticsearch-stock-aws"},"index":{"number\_of\_shards":"32","number\_of\_replicas":"2","similarity":{"default":{"type":"custom\_fotolia"}}},"foreground":"yes","transport":{"tcp":{"compress":"true"}},"pqcode\_plugin":{"encoder\_blob\_path":"config/pq-encoder/stock2.encoder"},"bootstrap":{"mlockall":"true"},"threadpool":{"bulk":{"queue\_size":"1000"}},"cloud":{"aws":{"region":"eu-west-1"}},"path":{"conf":"/etc/elasticsearch/elasticsearch.yml","data":"/mnt/","logs":"/usr/share/elasticsearch/logs","work":"/mnt/","home":"/usr/share/elasticsearch"},"node":{"data":"true","name":"aws-elasticsearch-3","master":"true"},"discovery":.....

Then I kept get the **error** message:  
[warning][elasticsearch] Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)

---

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 9:52pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/4 "2016-10-05T21:52:46Z")

</div>

Shall I change anything in elasticsearch.yml?

---

<div class="post-metadata">

### Author: ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [October 5, 2016, 10:06pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/5 "2016-10-05T22:06:00Z")

</div>

Most likely you just want to set elasticsearch.url to `192.168.0.194:9300` or `ip-192-168-0-194.eu-west-1.compute.internal:9300`. Elasticsearch needs to bind to whatever public address you're trying to connect to, so yes you'll need to update elasticsearch.yml if you haven't already.

---

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 10:12pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/6 "2016-10-05T22:12:31Z")

</div>

Is below right?  
ES still tries to connect 127.0.0.1...

I changed elasticsearch.yml in network portion:

# ---------------------------------- Network -----------------------------------

# 

# Set the bind address to a specific IP (IPv4 or IPv6):

# 

# network.host: 192.168.0.194

# 

# Set a custom port for HTTP:

# 

# http.port: 9300

As well as Discover portion:

# --------------------------------- Discovery ----------------------------------

# 

# Pass an initial list of hosts to perform discovery when new node is started:

# The default list of hosts is ["192.168.0.194"]

# 

# discovery.zen.ping.multicast.enabled: false

# discovery.zen.ping.unicast.hosts: ["192.168.0.238","192.168.0.237","192.168.0.208","192.168.0.181"]

---

<div class="post-metadata">

### Author: ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [October 5, 2016, 10:15pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/7 "2016-10-05T22:15:14Z")

</div>

Looks ok to me. You might want to ask in the Elasticsearch forum. Once Elasticsearch is accessible on a non-loopback address it should be easy to connect Kibana.

---

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 10:19pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/8 "2016-10-05T22:19:00Z")

</div>

Ok, last question, these changes in elasticsearch.yml are all in comments....DO they really work?

---

<div class="post-metadata">

### Author: ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [October 5, 2016, 10:29pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/9 "2016-10-05T22:29:58Z")

</div>

You'll definitely need to uncomment any lines you want to make active.

---

<div class="post-metadata">

### Author: ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)
#### Post date: [October 5, 2016, 10:55pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/10 "2016-10-05T22:55:25Z")

</div>

i solved it. It is version compatible between Kibana and ES.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:37pm UTC](https://discuss.elastic.co/t/how-can-i-use-kibana-to-see-indices-in-another-es-cluster/62306/11 "2017-07-06T13:37:22Z")

</div>


