Hi, I am wondering what the path.data compared to path.settings.
I was deploying a couple of .conf files under /etc/logstash/conf.d/ directory via cmd line and it complained that it cannot find the --path.settings and switched to default.
Does re-starting logstash service automatically loads the path.settings and reads the new configs?
I might sound like a smart-ass, but: path.data is the directory for the data of Logstash and path.settings is the path for the settings … To be more precise: The ‚data‛ is everything that Logstash saves on the hard drive while executing its pipelines, e.g the event information from the persistent queue and other status information that it might need in case of a crash or restart. The ‚settings‛ are the yml and conf files that tell Logstash what to do.
Your configuration changes should be applied whenever Logstash is restarted or a SIGHUP signal is sent or if the automatic reload is activated.
Thank you for the quick response. I enabled the 'automatic reload' option but maybe got a bit tangled up as I also re-started the service at the same time.
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.