# Independant monitoring cluster **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-monitoring\ **Created:** [February 7, 2019, 12:06pm UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444 "2019-02-07T12:06:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [February 7, 2019, 12:06pm UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/1 "2019-02-07T12:06:03Z")
Unable to create a separate cluster for Monitoring the Elastic stack. I have tried configuring it via both MetricBeat as well as HTTP exporters, but I do not see the monitoring information for my production cluster. All I see is the monitoring stats for the monitoring cluster itself. I am running the trial license on the monitoring cluster, and basic on the production cluster. ---
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [February 7, 2019, 12:12pm UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/2 "2019-02-07T12:12:57Z")
Using metricbeat, I am able to get metric information about Elasticsearch, but it is not visible in the monitoring UI of Kibana ---
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [February 7, 2019, 4:09pm UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/3 "2019-02-07T16:09:37Z")
Hi @NerdSec, what exactly do you want to do? Also, this is the Elasticsearch area and this sounds more like a Kibana issue... Anyway, with the basic license Kibana will only be able to monitor one Elasticsearch cluster, the one to which the Elasticsearch node that Kibana is configured to connect to belongs. Why would you like to have a separate monitoring cluster? There is probably a good reason but I can't think of one... Also, which parts of Elastic Stack do you want to monitor? You might have to enable monitoring from some parts e.g. for [Logstash](https://www.elastic.co/guide/en/logstash/6.5/logstash-monitoring-overview.html) > Unlike X-Pack monitoring for Elasticsearch and Kibana, there is no `xpack.monitoring.collection.enabled` setting on Logstash. You must use the `xpack.monitoring.enabled` setting to enable and disable data collection. Basic Elasticsearch and Kibana monitoring is enabled by default I think... ---
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [February 8, 2019, 4:11am UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/4 "2019-02-08T04:11:17Z")
> [@A\_B](#): > > Anyway, with the basic license Kibana will only be able to monitor one Elasticsearch cluster, the one to which the Elasticsearch node that Kibana is configured to connect to belongs. Can I not forward that data to a separate elasticsearch instance? We are running a prod setup and want to monitor this regularly, till we get a gold/platinum license. Also, there is a lot of data already on the cluster and it just clutters everything up. Spaces has solved the issue to some extent, but it is recommended in the guide to have a separate monitoring instance. > [Monitoring in a production environment | Elastic Stack Overview [7.4] | Elastic](https://www.elastic.co/guide/en/elastic-stack-overview/current/monitoring-production.html) > [@A\_B](#): > > Also, which parts of Elastic Stack do you want to monitor? You might have to enable monitoring from some parts The issue is only for elasticsearch and kibana. ---
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [February 8, 2019, 6:02am UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/5 "2019-02-08T06:02:15Z")
The issue is resolved. For the sake of others who would like to do this, here are the settings I made: My production cluster has the following cluster settings: ```auto { "persistent" : { "xpack" : { "monitoring" : { "elasticsearch" : { "collection" : { "enabled" : "true" } }, "collection" : { "enabled" : "true" } } } }, "transient" : { } } ``` My monitoring cluster has the following cluster settings: ```auto { "persistent" : { "xpack" : { "monitoring" : { "elasticsearch" : { "collection" : { "enabled" : "false" } }, "collection" : { "enabled" : "true" } } } }, "transient" : { } } ``` And I have configure http exporters in elasticsearch.yml to point to my **Monitoring cluster**. I have then configured beats and logstash to send the monitoring data to my **Production cluster** , and not the **Monitoring cluster**. Also, I have disabled kibana monitoring the `kibana.yml`. ```auto xpack.monitoring.kibana.collection.enabled: false ``` Post this and deleting all the existing `.monitoring*` indices on my **Monitoring cluster** , I was able to view the monitoring data in the Kibana UI. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 8, 2019, 6:02am UTC](https://discuss.elastic.co/t/independant-monitoring-cluster/167444/6 "2019-03-08T06:02:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.