# FileBeat 6.4.0 on Windows as non-service app and environment variables

**URL:** <https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 30, 2018, 10:26am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677 "2018-08-30T10:26:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![prwillmot](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@prwillmot](https://discuss.elastic.co/u/prwillmot)\
**Post date:** [August 30, 2018, 10:26am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/1 "2018-08-30T10:26:59Z")

</div>

With FileBeat 6.4.0 on Windows (running as a stand-alone app from command line, not a service) we are trying to use various environment variable string values as custom field values per reference document content at [https://www.elastic.co/guide/en/beats/filebeat/current/using-environ-vars.html](https://www.elastic.co/guide/en/beats/filebeat/current/using-environ-vars.html)

with windows SET command we can definitely see env var values are valid (note: sudo-type concerns do not apply)

but in config file (which works perfectly for everything except these custom field values) we do as follows (assuming FIELD\_1 and FIELD\_2 have valid environment variable values from SET):

fields:  
field\_1: $(FIELD\_1)  
field\_2: $(FIELD\_2)

In the output, all we get is the literal "$(FIELD\_1)" string embedded in the field values - eg. in JSON "field\_1":"$(FIELD\_1)"

env variable value substition does not appear to be working

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [August 31, 2018, 4:41pm UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/2 "2018-08-31T16:41:03Z")

</div>

The syntax for environment variables is `${FIELD_1}`. Do not use parens, but braces.

---

<div class="post-metadata">

**Author:** ![prwillmot](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@prwillmot](https://discuss.elastic.co/u/prwillmot)\
**Post date:** [September 7, 2018, 7:40am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/3 "2018-09-07T07:40:39Z")

</div>

Many thanks, works perfectly on Windows 7

---

<div class="post-metadata">

**Author:** ![kegnomotre](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@kegnomotre](https://discuss.elastic.co/u/kegnomotre)\
**Post date:** [September 9, 2018, 6:59am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/4 "2018-09-09T06:59:40Z")

</div>

Hey priwillmot did you managed to figure out the way to solve?

With Regards,  
Kegno Motre [https://dltutuapp.com/tutuapp-download/](https://dltutuapp.com/tutuapp-download/)  
[https://showbox.run/](https://showbox.run/)  
[https://kodi.software/](https://kodi.software/)

---

<div class="post-metadata">

**Author:** ![prwillmot](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@prwillmot](https://discuss.elastic.co/u/prwillmot)\
**Post date:** [September 10, 2018, 5:37am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/5 "2018-09-10T05:37:29Z")

</div>

Hi

The proposed solution from Steffen to use { insead of ( worked perfectly for my windows scenario

---

<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:** [October 8, 2018, 5:37am UTC](https://discuss.elastic.co/t/filebeat-6-4-0-on-windows-as-non-service-app-and-environment-variables/146677/6 "2018-10-08T05:37:29Z")

</div>

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