# Basic license with seperate monitoring cluster
**URL:** https://discuss.elastic.co/t/basic-license-with-seperate-monitoring-cluster/67546
**Category:** Elasticsearch
**Created:** [November 29, 2016, 9:07pm UTC](https://discuss.elastic.co/t/basic-license-with-seperate-monitoring-cluster/67546 "2016-11-29T21:07:48Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Zfs](https://discuss.elastic.co/u/Zfs)
#### Post date: [November 29, 2016, 9:07pm UTC](https://discuss.elastic.co/t/basic-license-with-seperate-monitoring-cluster/67546/1 "2016-11-29T21:07:48Z")
Hi,
With marvel on 2.4.X I could run a separate monitoring cluster and have my main cluster send metrics to that cluster. I did not monitor the monitoring cluster so I would only be monitoring the main cluster.
I've deployed elasticsearch v5 to do the same, but it appears kibana expects x-pack to also be deployed to the current elasticsearch cluster as I now receive the below when trying to access kibana web interface:
```
plugin:xpack_main@5.0.1 X-Pack plugin is not installed on Elasticsearch cluster
```
However if I deploy x-pack to the monitoring cluster then the basic license will not support monitoring more than 1 cluster. It unfortunately selects the current cluster to monitor rather than my main cluster. Is there a way to select which cluster to monitor using the basic license?
Thanks
---
### Author:  [@Zfs](https://discuss.elastic.co/u/Zfs)
#### Post date: [November 29, 2016, 9:21pm UTC](https://discuss.elastic.co/t/basic-license-with-seperate-monitoring-cluster/67546/2 "2016-11-29T21:21:52Z")
Just had to turn off all the x-pack features within the monitoring cluster.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 27, 2016, 9:22pm UTC](https://discuss.elastic.co/t/basic-license-with-seperate-monitoring-cluster/67546/3 "2016-12-27T21:22:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.