# Setting up a Separate Monitoring Cluster **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [July 4, 2016, 12:04pm UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645 "2016-07-04T12:04:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Geeshan\_S](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@Geeshan\_S](https://discuss.elastic.co/u/Geeshan_S)\ **Post date:** [July 4, 2016, 12:04pm UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/1 "2016-07-04T12:04:36Z")
Hi All, I'm trying to setup a separate cluster(kibanacluster) for monitoring my primary elasticsearch cluster (marveltest) . Below are the ES, Marvel and Kibana versions I'm using. The ES version is fixed for the moment. I can update or downgrade the other components if needed. kibana-4.4.1 elasticsearch-2.2.1 marvel-agent-2.2.1 The monitoring cluster and Kibana are both running in the host 192.168.2.124 and the primary cluster is running in a separate host 192.168.2.116. 192.168.2.116: elasticsearch.yml has the below entry marvel.agent.exporter.es.hosts: ["192.168.2.124"] marvel.enabled: true marvel.agent.exporters: id1: type: http host: ["[http://192.168.2.124:9200](http://192.168.2.124:9200)"] Looking at the DEBUG logs in the monitoring cluster i can see data is coming from the primary cluster but is getting "filtered" since the cluster name is different. ...... [2016-07-04 16:33:25,144][DEBUG][transport.netty] [nodek] connected to node [{#zen\_unicast\_2#}{192.168.2.124}{192.168.2.124:9300}] [2016-07-04 16:33:25,144][DEBUG][transport.netty] [nodek] connected to node [{#zen\_unicast\_1#}{192.168.2.116}{192.168.2.116:9300}] **[2016-07-04 16:33:25,183][DEBUG][discovery.zen.ping.unicast] [nodek] [1] filtering out response from {node1}{Rmgg0Mw1TSmIpytqfnFgFQ}{192.168.2.116}{192.168.2.116:9300}, not same cluster\_name [marveltest]** [2016-07-04 16:33:26,533][DEBUG][discovery.zen.ping.unicast] [nodek] [1] filtering out response from {node1}{Rmgg0Mw1TSmIpytqfnFgFQ}{192.168.2.116}{192.168.2.116:9300}, not same cluster\_name [marveltest] [2016-07-04 16:33:28,039][DEBUG][discovery.zen.ping.unicast] [nodek] [1] filtering out response from {node1}{Rmgg0Mw1TSmIpytqfnFgFQ}{192.168.2.116}{192.168.2.116:9300}, not same cluster\_name [marveltest] [2016-07-04 16:33:28,040][DEBUG][transport.netty] [nodek] disconnecting from [{#zen\_unicast\_2#}{192.168.2.124}{192.168.2.124:9300}] due to explicit disconnect call [2016-07-04 16:33:28,040][DEBUG][discovery.zen] [nodek] filtered ping responses: (filter\_client[true], filter\_data[false]) --\> ping\_response{node [{nodek}{vQ-Iq8dKSz26AJUX77Ncfw}{192.168.2.124}{192.168.2.124:9300}], id[42], master [{nodek}{vQ-Iq8dKSz26AJUX77Ncfw}{192.168.2.124}{192.168.2.124:9300}], hasJoinedOnce [true], cluster\_name[kibanacluster]} [2016-07-04 16:33:28,053][DEBUG][transport.netty] [nodek] disconnecting from [{#zen\_unicast\_1#}{192.168.2.116}{192.168.2.116:9300}] due to explicit disconnect call [2016-07-04 16:33:28,057][DEBUG][transport.netty] [nodek] connected to node [{nodek}{vQ-Iq8dKSz26AJUX77Ncfw}{192.168.2.124}{192.168.2.124:9300}] [2016-07-04 16:33:28,117][DEBUG][discovery.zen.publish] [nodek] received full cluster state version 32 with size 5589 ..... Thank you, Geeshan ---
**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:** [July 4, 2016, 10:57pm UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/2 "2016-07-04T22:57:02Z")
Please don't post pictures of text, they are difficult to read and some people may not be even able to see them. Did you follow the docs, here - [https://www.elastic.co/guide/en/marvel/2.2/installing-marvel.html#monitoring-cluster](https://www.elastic.co/guide/en/marvel/2.2/installing-marvel.html#monitoring-cluster) ---
**Author:** ![Geeshan\_S](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@Geeshan\_S](https://discuss.elastic.co/u/Geeshan_S)\ **Post date:** [July 5, 2016, 3:50am UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/3 "2016-07-05T03:50:26Z")
Sorry about that. I have edited the post. Yes I followed the above link in setting it up. Could this be a licence issue? Since there are two clusters involved? ---
**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:** [July 5, 2016, 5:32am UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/4 "2016-07-05T05:32:13Z")
It's not a license issue. Can you show the `elasticsearch.yml` file of each (but remove comments, and empty lines). ---
**Author:** ![Geeshan\_S](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@Geeshan\_S](https://discuss.elastic.co/u/Geeshan_S)\ **Post date:** [July 10, 2016, 5:16am UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/5 "2016-07-10T05:16:42Z")
Hi Mark, Below are the elasticsearch.yml files. **2.116 (Primary cluster)** [cluster.name](http://cluster.name): marveltest [node.name](http://node.name): node1 bootstrap.mlockall: true network.host: 192.168.2.116 discovery.zen.ping.unicast.hosts: ["192.168.2.124", "192.168.2.116"] gateway.recover\_after\_nodes: 1 gateway.expected\_nodes: 1 gateway.recover\_after\_time: 1m path.repo: ["/usr/local/surf/ES\_BACKUP"] script.inline: true script.indexed: true **2.124(Monitoring Cluster)** [cluster.name](http://cluster.name): kibanacluster [node.name](http://node.name): nodek node.master: false node.data: false network.host: 192.168.2.124 discovery.zen.ping.unicast.hosts: ["192.168.2.116", "192.168.2.124"] ---
**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:** [July 10, 2016, 5:50am UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/6 "2016-07-10T05:50:08Z")
I'd suggest you read [https://www.elastic.co/guide/en/marvel/current/installing-marvel.html#monitoring-cluster](https://www.elastic.co/guide/en/marvel/current/installing-marvel.html#monitoring-cluster), as I mentioned. However you don't point each cluster discovery at the other node. ---
**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:42pm UTC](https://discuss.elastic.co/t/setting-up-a-separate-monitoring-cluster/54645/7 "2017-07-06T13:42:40Z")