# Beats monitoring settings

**URL:** <https://discuss.elastic.co/t/beats-monitoring-settings/238882>\
**Category:** Beats\
**Created:** [June 26, 2020, 3:37pm UTC](https://discuss.elastic.co/t/beats-monitoring-settings/238882 "2020-06-26T15:37:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ronin](https://avatars.discourse-cdn.com/v4/letter/r/ad7895/32.png) [@Ronin](https://discuss.elastic.co/u/Ronin)\
**Post date:** [June 26, 2020, 3:37pm UTC](https://discuss.elastic.co/t/beats-monitoring-settings/238882/1 "2020-06-26T15:37:58Z")

</div>

We are using Elastic Cloud and its unclear from the documentation of what we should put for the monitoring settings. Following this documentation: [https://www.elastic.co/guide/en/beats/filebeat/current/monitoring-internal-collection.html](https://www.elastic.co/guide/en/beats/filebeat/current/monitoring-internal-collection.html)

Take that we have two clusters, Staging and Monitoring. In Cloud, Staging is setup to send its monitoring to the Monitoring Cluster. In the documentation, the example shows we would put the cloud.id and cloud.auth to the Staging cluster and not the Monitoring cluster. When doing this, the beats instance will not show up in the Monitoring cluster. We have also tried to set the cloud.id and cloud.auth to the Monitoring cluster with no success. To note, if we remove the cloud settings and use the direct elasticsearch endpoint, auth, and cluster\_uuid settings this will work.

---

<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:** [July 24, 2020, 5:38pm UTC](https://discuss.elastic.co/t/beats-monitoring-settings/238882/2 "2020-07-24T17:38:02Z")

</div>

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