# Beats Internal monitoring

**URL:** <https://discuss.elastic.co/t/beats-internal-monitoring/255350>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [November 13, 2020, 2:02pm UTC](https://discuss.elastic.co/t/beats-internal-monitoring/255350 "2020-11-13T14:02:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MR\_551](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@MR\_551](https://discuss.elastic.co/u/MR_551)\
**Post date:** [November 13, 2020, 2:02pm UTC](https://discuss.elastic.co/t/beats-internal-monitoring/255350/1 "2020-11-13T14:02:44Z")

</div>

Hello everyone,

Has anyone experienced an issue with internal monitoring for Beats? When i ship internal metrics for each Beat to a monitoring cluster, they get grouped under the same Beat on Stack Monitoring tab. I am also using a unique name for each Metricbeat.

Here is a piece of Metricbeat config for internal monitoring.

```auto
# ============================= X-Pack Monitoring ==============================
monitoring:
  enabled: true
  cluster_uuid: #my cluster uuid here#

# Metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Metricbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

```

Let me know if i need to provide additional info. Any help is appreciated!

---

<div class="post-metadata">

**Author:** ![abrx](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abrx/32/43881_2.png) [@abrx](https://discuss.elastic.co/u/abrx)\
**Post date:** [November 13, 2020, 2:25pm UTC](https://discuss.elastic.co/t/beats-internal-monitoring/255350/2 "2020-11-13T14:25:03Z")

</div>

Have you configured name and tags for your beats as explained [here](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-general-options.html#configuration-general) ?  
By default it should use the hostname but I don't know how works Monitoring under the hood...

---

<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:** [December 11, 2020, 2:25pm UTC](https://discuss.elastic.co/t/beats-internal-monitoring/255350/3 "2020-12-11T14:25:14Z")

</div>

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