# Missing modules.path

**URL:** <https://discuss.elastic.co/t/missing-modules-path/132161>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [May 16, 2018, 2:54pm UTC](https://discuss.elastic.co/t/missing-modules-path/132161 "2018-05-16T14:54:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Invictus](https://avatars.discourse-cdn.com/v4/letter/i/bc79bd/32.png) [@Invictus](https://discuss.elastic.co/u/Invictus)\
**Post date:** [May 16, 2018, 2:54pm UTC](https://discuss.elastic.co/t/missing-modules-path/132161/1 "2018-05-16T14:54:57Z")

</div>

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](https://discuss.elastic.co/t/docker-module-doesnt-send-healthcheck-info/122001/6):
>
> 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?

---

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [May 17, 2018, 8:55am UTC](https://discuss.elastic.co/t/missing-modules-path/132161/2 "2018-05-17T08:55:57Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Invictus](https://avatars.discourse-cdn.com/v4/letter/i/bc79bd/32.png) [@Invictus](https://discuss.elastic.co/u/Invictus)\
**Post date:** [May 17, 2018, 1:06pm UTC](https://discuss.elastic.co/t/missing-modules-path/132161/3 "2018-05-17T13:06:35Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![gungorsa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gungorsa/32/31594_2.png) [@gungorsa](https://discuss.elastic.co/u/gungorsa)\
**Post date:** [May 25, 2018, 9:02am UTC](https://discuss.elastic.co/t/missing-modules-path/132161/4 "2018-05-25T09:02:42Z")

</div>

Hi Invictus,

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

Thanks

---

<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:** [June 22, 2018, 9:02am UTC](https://discuss.elastic.co/t/missing-modules-path/132161/5 "2018-06-22T09:02:45Z")

</div>

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