# Fixing Legacy 'Self Monitoring' for Docker containers

**URL:** <https://discuss.elastic.co/t/fixing-legacy-self-monitoring-for-docker-containers/262151>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [January 25, 2021, 5:39pm UTC](https://discuss.elastic.co/t/fixing-legacy-self-monitoring-for-docker-containers/262151 "2021-01-25T17:39:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![doyelese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doyelese/32/82871_2.png) [@doyelese](https://discuss.elastic.co/u/doyelese)\
**Post date:** [January 25, 2021, 5:39pm UTC](https://discuss.elastic.co/t/fixing-legacy-self-monitoring-for-docker-containers/262151/1 "2021-01-25T17:39:11Z")

</div>

I am getting the warning that Self Monitoring will not be supported in 8.0. My elastic environment is configured via 5 ElasticSearch container nodes and 1 Kibana container.

How do I migrate away from self monitoring the containers if the containers are responsible for the environment? Do I put metricbeat on the server that is hosting the containers and have the containers report there instead of within the containers themselves?

 ![Screen Shot 2021-01-25 at 10.34.04 AM](https://us1.discourse-cdn.com/elastic/original/3X/4/5/4597ec6e186e47628826bdda358291324183a312.png)

This link

> **[Collecting Elasticsearch monitoring data with Metricbeat | Elasticsearch...](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html)**

is not particularly helpful in my understanding of getting off of legacy for docker environments since step 2/3 require installing Metricbeat onto the Elasticsearch node (counter to docker methodology of 1 process per container)

---

<div class="post-metadata">

**Author:** ![doyelese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doyelese/32/82871_2.png) [@doyelese](https://discuss.elastic.co/u/doyelese)\
**Post date:** [January 25, 2021, 5:56pm UTC](https://discuss.elastic.co/t/fixing-legacy-self-monitoring-for-docker-containers/262151/2 "2021-01-25T17:56:29Z")

</div>

Fixed this - for anyone curious or searching it was.

1. Install metricbeat on the host machine and configure like instructed on [https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html)

2. Change modules.d/elasticsearch-xpack.yml setting from scope: node to scope: cluster

3. Kibana should give you a prompt saying 'Disable self-monitoring to finish migration'

---

<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:** [February 22, 2021, 5:56pm UTC](https://discuss.elastic.co/t/fixing-legacy-self-monitoring-for-docker-containers/262151/3 "2021-02-22T17:56:33Z")

</div>

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