# Adding a new and different ElasticSearch node to Kibana

**URL:** <https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277>\
**Category:** Elasticsearch\
**Created:** [May 9, 2022, 5:33pm UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277 "2022-05-09T17:33:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![leonardof131](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leonardof131](https://discuss.elastic.co/u/leonardof131)\
**Post date:** [May 9, 2022, 5:33pm UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277/1 "2022-05-09T17:33:36Z")

</div>

I've seen some similar posts on the forum but none of them quite represents my issue.

I've got an Elasticsearch instance running receiving some logs, and Kibana in a separete instance pointed to it. Everything works great, I can see all of my indexes, stack monitoring is showing disk and cpu usage of the ES instance.

Now here's my problem: I want to add a new ES instance to the mix. It will receive completely different logs from completely different applications.  
Is this possible ?

**Cross-cluster search** dosen't seem to be the solution, as I dont want to run a single search request against one or more remote clusters, but be able to see different index and run different search requests on them from an single Kibana instance.

So far generating new certificates for the ES Instances (either new certificates for both or creating a new certificate for one node and copying to the other) isn't working.

Any help ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 9, 2022, 5:39pm UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277/2 "2022-05-09T17:39:27Z")

</div>

Cross-cluster search is the only way to query multiple clusters from a single Kibana instance.

---

<div class="post-metadata">

**Author:** ![leonardof131](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leonardof131](https://discuss.elastic.co/u/leonardof131)\
**Post date:** [May 9, 2022, 5:44pm UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277/3 "2022-05-09T17:44:35Z")

</div>

Thank you for your fast response!

Does Cross-cluster search works even if the two ES nodes have different data and indexes ?

---

<div class="post-metadata">

**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:** [May 10, 2022, 12:23am UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277/4 "2022-05-10T00:23:56Z")

</div>

Welcome to our community! 😃

Yes it does.

---

<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:** [June 7, 2022, 12:24am UTC](https://discuss.elastic.co/t/adding-a-new-and-different-elasticsearch-node-to-kibana/304277/5 "2022-06-07T00:24:26Z")

</div>

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