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

Elastic Stack Beats
1

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)
2

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