# Marvel - monitoring multiple ES clusters by one Monitoring ES cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [March 28, 2014, 1:05pm UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678 "2014-03-28T13:05:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![aristechnologypartne](https://avatars.discourse-cdn.com/v4/letter/a/b38774/32.png) [@aristechnologypartne](https://discuss.elastic.co/u/aristechnologypartne)\ **Post date:** [March 28, 2014, 1:05pm UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678/1 "2014-03-28T13:05:56Z")
Hi there, I have installed a 3 node ES "Monitoring[http://www.elasticsearch.org/guide/en/marvel/current/index.html](http://www.elasticsearch.org/guide/en/marvel/current/index.html)" cluster and configured two other ES clusters (10 nodes one an 3 nodes one) to send data to it. The data gathering / storage seems to be working fine, but the display using "latest" Marvel UI a bit confusing. For example, on "Cluster Overview" page, how does one should pick a specific ES Cluster? At the moment, the "Cluster Summary" is jumping between two ES cluster I have seems to me randomly. I did try to add query criteria on top to make it choose to no avail... That said, the "Nodes" panel on the same page works as expected - i.e. by defaults it show all reporting nodes (from both cluster), but if I specify "Filter" there, I do get information about Nodes of a specific cluster. I'm new to Marvel and above may seems a bit naive, but in its current form, does "latest" Marvel was intended to support my Use Case? Thx. Thanks for your help. Regards, Me. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d621ccb4-3a71-4e45-a96a-985298122f79%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d621ccb4-3a71-4e45-a96a-985298122f79%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [April 1, 2014, 12:09pm UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678/2 "2014-04-01T12:09:42Z")
Hi Me, At the moment marvel doesn't support monitoring multiple production clusters with a single monitoring one. Working on it! Cheers, Boaz On Friday, March 28, 2014 2:05:56 PM UTC+1, me wrote: > Hi there, > > I have installed a 3 node ES "Monitoring[http://www.elasticsearch.org/guide/en/marvel/current/index.html](http://www.elasticsearch.org/guide/en/marvel/current/index.html)" > cluster and configured two other ES clusters (10 nodes one an 3 nodes one) > to send data to it. The data gathering / storage seems to be working fine, > but the display using "latest" Marvel UI a bit confusing. For example, on > "Cluster Overview" page, how does one should pick a specific ES Cluster? At > the moment, the "Cluster Summary" is jumping between two ES cluster I have > seems to me randomly. I did try to add query criteria on top to make it > choose to no avail... > > That said, the "Nodes" panel on the same page works as expected - i.e. by > defaults it show all reporting nodes (from both cluster), but if I specify > "Filter" there, I do get information about Nodes of a specific cluster. > > I'm new to Marvel and above may seems a bit naive, but in its current > form, does "latest" Marvel was intended to support my Use Case? Thx. > > Thanks for your help. > > Regards, Me. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1d741ed0-5072-469b-993c-2e68cde8e573%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1d741ed0-5072-469b-993c-2e68cde8e573%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![W\_Koot](https://avatars.discourse-cdn.com/v4/letter/w/5f8ce5/32.png) [@W\_Koot](https://discuss.elastic.co/u/W_Koot)\ **Post date:** [October 1, 2014, 12:59pm UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678/3 "2014-10-01T12:59:00Z")
Hi Boaz, Looking forward to the update. I presume this will also address the "Warning: Multiple masters. 2 nodes report master role" of the nodes panel? 🙂 Perhaps it is possible to also use the cluster to differentiate between indices? Currently it seems like Marvel groups all data for indices based on its name alone. We have several clusters with the same index name (don't ask me why 😉 ), which makes the index metrics useless since there is no distinction between clusters. gr, -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5da62028-054e-48a4-857f-58a3ab652275%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5da62028-054e-48a4-857f-58a3ab652275%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [October 6, 2014, 2:47pm UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678/4 "2014-10-06T14:47:04Z")
On Wednesday, October 1, 2014 2:59:00 PM UTC+2, W Koot wrote: > Hi Boaz, > > Looking forward to the update. > I presume this will also address the "Warning: Multiple masters. 2 nodes > report master role" of the nodes panel? 🙂 If you monitor two clusters, you will have multiple masters - which is for a single cluster is a big no no. Multi cluster support in marvel will obviously address this. > Perhaps it is possible to also use the cluster to differentiate between > indices? Currently it seems like Marvel groups all data for indices based on its name alone. > We have several clusters with the same index name (don't ask me why 😉 ), > which makes the index metrics useless since there is no distinction between > clusters. We will use the cluster uuid to filter the data when displaying it. Same name indices shouldn't be a problem. > gr, -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6160d6d6-2b13-469e-a3f6-084260b26eb3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6160d6d6-2b13-469e-a3f6-084260b26eb3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:58am UTC](https://discuss.elastic.co/t/marvel-monitoring-multiple-es-clusters-by-one-monitoring-es-cluster/16678/5 "2017-07-06T00:58:06Z")