# Beats logging into custom path prevented by -e global flag in systemd unit

**URL:** <https://discuss.elastic.co/t/beats-logging-into-custom-path-prevented-by-e-global-flag-in-systemd-unit/186118>\
**Category:** Beats\
**Created:** [June 17, 2019, 5:00pm UTC](https://discuss.elastic.co/t/beats-logging-into-custom-path-prevented-by-e-global-flag-in-systemd-unit/186118 "2019-06-17T17:00:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thekm1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thekm1/32/35926_2.png) [@thekm1](https://discuss.elastic.co/u/thekm1)\
**Post date:** [June 17, 2019, 5:00pm UTC](https://discuss.elastic.co/t/beats-logging-into-custom-path-prevented-by-e-global-flag-in-systemd-unit/186118/1 "2019-06-17T17:00:41Z")

</div>

In the filebeat version 7.x there is an entry created in the systemd unit of filebeat `Environment="BEAT_LOG_OPTS=-e"`. This entry overwrites the settings inside the .yml file for `logging.to_files: true`

If you are updating from 6.x version to 7.x then this entry in systemd unit is new and needs to get deleted if you want to log to a custom path.

I got actually 2 questions know.

1. Is this really ment to be ? because as you can't overwrite it from the .yml file it seems "buggisious" and confusing.
2. in which priority does configuring variables work (.yml file, at startup, etc)

---

<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:** [July 15, 2019, 7:00pm UTC](https://discuss.elastic.co/t/beats-logging-into-custom-path-prevented-by-e-global-flag-in-systemd-unit/186118/2 "2019-07-15T19:00:42Z")

</div>

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