Missing modules.path

[Invictus]

hi members,

as already pointed out in that request it seems necessary to enable healthcheck inside the container.

Docker module doesn't send healthcheck info

Thanks for the pointers. Turns out I was the one who missed something simple...I did not realize you need to enable healthcheck on the docker container side . I thought it was a metric that was automatically generated (similar to the other metrics, such as "container", "cpu", "memory", etc.). I exposed the healthcheck in a docker container and now metricbeat does indeed publish healthcheck entries. Thanks for your help!

So I tried to set the following commands in the container with these errors.

[root@c1c93cf2f46d metricbeat]# metricbeat modules list
Error in modules manager: modules management requires 'metricbeat.config.modules.path' setting
[root@c1c93cf2f46d metricbeat]# metricbeat modules enable healthcheck
Error in modules manager: modules management requires 'metricbeat.config.modules.path' setting

So when I set such module.path in my metricbeat.yml there will be no more docker metrics transmitted to Elasticsearch.

This is my current metricbeat.yml:

metricbeat.modules:
- module: docker
  metricsets:
    - container
    - cpu
    - diskio
    - healthcheck
    - info
    - memory
    - network
  hosts: ["unix:///var/run/docker.sock"]
  period: 10s
  enable: true

setup.dashboards.enabled: true
setup.kibana:
  host: "10.251.6.190:5601"

output.elasticsearch:
  hosts: ["elasticsearch-coordinating:9200"]

So is there something wrong with the configuration?

[adrisr (Adrian Serrano)]

Inside the docker module you have specified enable: true where it should be enabled: true

[Invictus]

Ok thanks.
I changed it, but the Errors still exist. He is still complaining to the required 'metricbeat.config.modules.path'.
Does the metricbeat directory need to have a certain structure?

[gungorsa (Güngör Sarıcıoğlu)]

Hi Invictus,

Did you solve this issue? İf you solved this issue . Could you share solution?

Thanks