Fixing Legacy 'Self Monitoring' for Docker containers

Elastic Stack Elasticsearch
1

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
Screen Shot 2021-01-25 at 10.34.04 AM1093×883 55.9 KB

This link

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)

2

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

  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'

    Screen Shot 2021-01-25 at 10.56.15 AM
    Screen Shot 2021-01-25 at 10.56.15 AM809×971 54.8 KB

3

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