# Could we monitor multiple ES clusters using a single Monitoring ES cluster?

**URL:** https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472
**Category:** Elasticsearch
**Created:** [August 1, 2018, 6:16am UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472 "2018-08-01T06:16:42Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![sahil\_sawhney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sahil_sawhney/32/88932_2.png) [@sahil\_sawhney](https://discuss.elastic.co/u/sahil_sawhney)
#### Post date: [August 1, 2018, 6:16am UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/1 "2018-08-01T06:16:42Z")

</div>

I have a use case that i have 2 ES clusters let us say **es1** and **es2** , is it possible that i can monitor both of these clusters using a single monitring ES custer let us say **esMonit1**.

So what happens is when we enable xpack for es, an index is automatically created( **.monitoring-es-** \* ) that holds the collected metrices.

Now if both es1 and es2 clusters will push the monitoring indexes to the esMonit1 cluster, we wont be able to segregate the metrices basecd on es cluster.

So,  
Is there a workaround by which we can achieve the above mentioned use case or the only way is to have one monitoring ES cluster associated with one actual(containing application data) ES cluster.

---

<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: [August 1, 2018, 10:15am UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/2 "2018-08-01T10:15:49Z")

</div>

You can, but it's a feature of a Gold or above license - [https://www.elastic.co/subscriptions](https://www.elastic.co/subscriptions)

---

<div class="post-metadata">

### Author: ![sahil\_sawhney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sahil_sawhney/32/88932_2.png) [@sahil\_sawhney](https://discuss.elastic.co/u/sahil_sawhney)
#### Post date: [August 1, 2018, 12:16pm UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/3 "2018-08-01T12:16:28Z")

</div>

@warkolm Thanks for the reply

We have gold licence for elasticsearch. The problem is that both es1 and es2 would be pushing the metrices into same index ( .monitoring-es-\* ) over esMonit1. Hence what would be happening is that the monitoring es would be showing the aggregated result of all nodes and we would not be able to distinguish which node belong to which es cluster (es1 or es2)

---

<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: [August 1, 2018, 8:58pm UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/4 "2018-08-01T20:58:54Z")

</div>

> [@sahil\_sawhney](#):
>
> We have gold licence for elasticsearch

You should 100% reach out to your support engineer and check for an official response on this.

But you can drill into each cluster individually and it will filter nodes appropriately.

---

<div class="post-metadata">

### Author: ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)
#### Post date: [August 14, 2018, 11:39am UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/5 "2018-08-14T11:39:10Z")

</div>

Hi,  
Monitoring events contains the cluster\_uuid so this is still separated properly. We are doing this without any problems and each cluster is listed under monitoring.

Regards /Johan

---

<div class="post-metadata">

### Author: ![sahil\_sawhney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sahil_sawhney/32/88932_2.png) [@sahil\_sawhney](https://discuss.elastic.co/u/sahil_sawhney)
#### Post date: [August 14, 2018, 11:55am UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/6 "2018-08-14T11:55:20Z")

</div>

Thanks @JohanRask  
Just wanted to confirm, do we need to upload gold licence over data based ES and monitoring ES as well  
?  
Regards.

---

<div class="post-metadata">

### Author: ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)
#### Post date: [August 14, 2018, 12:03pm UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/7 "2018-08-14T12:03:06Z")

</div>

Yes, I think you have to. But remember that licenses are per node, not per cluster so we currently (pre-prod:ish 😉 ) have a single node monitoring cluster which is master+data. Not sure where this ends up but currently it is not realistic for us to have a real HA cluster for monitoring.

/Johan

---

<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: [September 11, 2018, 12:03pm UTC](https://discuss.elastic.co/t/could-we-monitor-multiple-es-clusters-using-a-single-monitoring-es-cluster/142472/8 "2018-09-11T12:03:17Z")

</div>

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