# Setup Marvel monitoring cluster

**URL:** https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205
**Category:** Kibana
**Created:** [January 30, 2017, 12:18pm UTC](https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205 "2017-01-30T12:18:14Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Zaid\_Amir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zaid_amir/32/54679_2.png) [@Zaid\_Amir](https://discuss.elastic.co/u/Zaid_Amir)
#### Post date: [January 30, 2017, 12:18pm UTC](https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205/1 "2017-01-30T12:18:14Z")

</div>

Hi,

I'm reading the installation documentation for Marvel and this grabbed my attention:

> Configure Kibana to connect to your monitoring cluster by setting the elasticsearch\_url property in the kibana.yml configuration file. For example:

> elasticsearch\_url: "[http://es-mon-1:9200](http://es-mon-1:9200)"

Now this works well if I only want to install Marvel on Kibana and have the marvel indices stored on a different cluster. But what if I want to have my own Kibana dashboard as well to visualize my work cluster? How can I tell Kibana to use two different clusters?

---

<div class="post-metadata">

### Author: ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)
#### Post date: [January 30, 2017, 10:12pm UTC](https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205/2 "2017-01-30T22:12:00Z")

</div>

@Zaid_Amir

In the kibana.yml, your monitoring cluster configuration is separate from the "production"-cluster.

So you'd have something like:

```auto
xpack:
 monitoring:
   elasticsearch:
     url: "http://localhost:9210"
     username: "kibana" # use built-in user
     password: "changeme"

```

But your elasticsearch production url would still be:

```auto
elasticsearch.url: "http://localhost:9200"

```

So you can use Kibana to visualize your production data (on `9200`), but you'll also can use the monitoring plugin in Kibana to see what's being collected in your monitoring cluster (on `9210`).

---

<div class="post-metadata">

### Author: ![Zaid\_Amir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zaid_amir/32/54679_2.png) [@Zaid\_Amir](https://discuss.elastic.co/u/Zaid_Amir)
#### Post date: [February 2, 2017, 7:23am UTC](https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205/3 "2017-02-02T07:23:04Z")

</div>

@thomasneirynck

Is this supported in ES 2.4?

---

<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: [March 2, 2017, 7:23am UTC](https://discuss.elastic.co/t/setup-marvel-monitoring-cluster/73205/4 "2017-03-02T07:23:05Z")

</div>

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