# Central Management: Wrong beat id

**URL:** <https://discuss.elastic.co/t/central-management-wrong-beat-id/160498>\
**Category:** Beats\
**Created:** [December 12, 2018, 8:21am UTC](https://discuss.elastic.co/t/central-management-wrong-beat-id/160498 "2018-12-12T08:21:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nick.e](https://avatars.discourse-cdn.com/v4/letter/n/8dc957/32.png) [@nick.e](https://discuss.elastic.co/u/nick.e)\
**Post date:** [December 12, 2018, 8:21am UTC](https://discuss.elastic.co/t/central-management-wrong-beat-id/160498/1 "2018-12-12T08:21:38Z")

</div>

Today I wanted to try out the new Central Management.  
For some reason, the metricbeat does not receive its configuration from central management.

I did the following steps:

1. Fresh installation of Elasticsearch and Kibana 6.5.3 on Debian with all necessary configurations (x-pack security etc.)
2. Downloaded metricbeat 6.5.3 for Windows x64 and unzipped the files to C:\Program Files\Metricbeat\6.5.3\ on a client
3. From the path named aboth I used the following command to enroll the beat:  
_metricbeat.exe enroll [http://kibana-ip:5601](http://kibana-ip:5601) --username elastic --password stdin_
4. After that the beat appeared in Central Management UI in Kibana. I added some tags (e.g. for Elasticsearch-Output)
5. Installed metricbeat as service and started it.

I expected it to now pull the configs from the Central Management. However, in Kibana the beat's Config Status only shows "Offline".  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b8d589907596a93de556a2bb2d249feb8cd22816.png)

Jumping back to the client's metricbeat log it shows the following line:

> error retriving new configurations, will use cached ones: Beat "1570704b-6f6d-4ada-801e-a16db6fc02c8" not found

1570704b-6f6d-4ada-801e-a16db6fc02c8 is the Beat's UUID. In Central Management the Beat's ID is completely different. May this be the cause?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/6/36d68e5841108a91feb2b052229f7beb62c676e6.png)

In a second try I enrolled the beat token-based. Same problem.

Am I missing any step?

---

<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:** [January 9, 2019, 10:21am UTC](https://discuss.elastic.co/t/central-management-wrong-beat-id/160498/2 "2019-01-09T10:21:42Z")

</div>

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