"This is the default base path for configuration files, including the main YAML configuration file", but wait, isn't this option actually defined filebeat.yml configuration ? according to this , it looks like filebeat is reading a configuration file which tells it the configuration file is in another location?
Thanks very much for identifying these issues in the documentation. In older versions of Filebeat, you had to specify the path to the config file when you started Filebeat in the foreground. This topic should have been updated when the default was added, but the topic was overlooked.
I've opened an issue in GitHub to track the doc issues that you've identified:
Please let us know if you are having any specific issues with Filebeat.
Thanks again for helping us improve the documentation.
it's all part me attempting to run filebeat as a service on raspberry pi,
another issue was until i directed all output from fileBeat to /dev/null
the service start simply hanged., it's it's all fine if you allready have a
service file, but when you don't it was extremely hard to see how to
configure, you have distros for linuxes but the tar ones' don't contain the
filebeat service ones.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.