Filebeat creates the keystore in the directory defined by the path.config configuration setting.
However, keystore is created in /path_where_tar_was_extracted/filebeat-7.2.0-linux-x86_64/data/ .
I have already defined path.config variable accordingly in filebeat.yml, but the behavior is not the expected.
I would suggest either to update the documentation to say that it is stored in path.data (instead of path.config) or to make Filebeat store it in path.config.
Hi,
obviously you have found a documentation inaccuracy on page, because source code tells exactly that it will be created under the data path by default. https://www.elastic.co/guide/en/beats/filebeat/current/keystore.html
I will open an issue for that so that this will be corrected:
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.