# Configuring Filebeat from a docker-compose.yml

**URL:** <https://discuss.elastic.co/t/configuring-filebeat-from-a-docker-compose-yml/209082>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 22, 2019, 3:12pm UTC](https://discuss.elastic.co/t/configuring-filebeat-from-a-docker-compose-yml/209082 "2019-11-22T15:12:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbwest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dbwest/32/32631_2.png) [@dbwest](https://discuss.elastic.co/u/dbwest)\
**Post date:** [November 22, 2019, 3:12pm UTC](https://discuss.elastic.co/t/configuring-filebeat-from-a-docker-compose-yml/209082/1 "2019-11-22T15:12:15Z")

</div>

I've noticed that there seems to be some Convention that maps nested config to environment variables along this pattern...

setting foo.bar.batz maps to env var FOO\_BAR\_BATZ.

How far does this extend and what percentage of a filebeat.yml file can we set just with environment variables.

---

<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:** [December 20, 2019, 3:12pm UTC](https://discuss.elastic.co/t/configuring-filebeat-from-a-docker-compose-yml/209082/2 "2019-12-20T15:12:32Z")

</div>

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