# Heartbeat processors variable in docker-compose file

**URL:** https://discuss.elastic.co/t/heartbeat-processors-variable-in-docker-compose-file/290582
**Category:** Beats
**Tags:** docker, heartbeat
**Created:** [November 30, 2021, 5:16pm UTC](https://discuss.elastic.co/t/heartbeat-processors-variable-in-docker-compose-file/290582 "2021-11-30T17:16:06Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)
#### Post date: [November 30, 2021, 5:16pm UTC](https://discuss.elastic.co/t/heartbeat-processors-variable-in-docker-compose-file/290582/1 "2021-11-30T17:16:06Z")

</div>

Hi,  
is it possible to provide variable required by a specific processor (i.e. add\_observer\_metadata) directly into docker-compose file?  
Something like:

`command: > heartbeat -e -E processors.add_observer_metadata.geo.name=London`

---

<div class="post-metadata">

### Author: ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)
#### Post date: [November 30, 2021, 7:16pm UTC](https://discuss.elastic.co/t/heartbeat-processors-variable-in-docker-compose-file/290582/2 "2021-11-30T19:16:59Z")

</div>

Since I cannot use only the environment variable without binding a config file I used this approach [Use environment variables in the configuration | Heartbeat Reference [master] | Elastic](https://www.elastic.co/guide/en/beats/heartbeat/master/using-environ-vars.html)

---

<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 28, 2021, 9:17pm UTC](https://discuss.elastic.co/t/heartbeat-processors-variable-in-docker-compose-file/290582/3 "2021-12-28T21:17:07Z")

</div>

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