# Filebeat creates a "Standalone Cluster" in Kibana Monitoring

**URL:** https://discuss.elastic.co/t/filebeat-creates-a-standalone-cluster-in-kibana-monitoring/188663
**Category:** Beats
**Tags:** elastic-stack-monitoring, filebeat
**Created:** [July 3, 2019, 9:19am UTC](https://discuss.elastic.co/t/filebeat-creates-a-standalone-cluster-in-kibana-monitoring/188663 "2019-07-03T09:19:10Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [July 3, 2019, 10:19am UTC](https://discuss.elastic.co/t/filebeat-creates-a-standalone-cluster-in-kibana-monitoring/188663/3 "2019-07-03T10:19:04Z")

</div>

Hi @Christophe_Journel and @DennisLoos,

In 7.2, we allowed Filebeat to ship its monitoring data directly to a Monitoring Elasticsearch cluster (which might be separate from your Production Elasticsearch cluster, where you send the log data being harvested by Filebeat). The new `monitoring.*` settings introduced in 7.2 let you set the Monitoring cluster for Filebeat.

Now, if your `output` is `elasticsearch`, then we **know** which Elasticsearch cluster your Filebeat is sending its logs data to. In that case the Monitoring UI can correctly associate the Filebeat instance with that Elasticsearch cluster.

However, if the `output` is something other than `elasticsearch`, we cannot know if the logs data is ending up in an Elasticsearch cluster. So the Monitoring UI shows the Filebeat instance in a "Standalone Cluster".

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-creates-a-standalone-cluster-in-kibana-monitoring/188663)._