When you want to use Logstash's pipeline feature the init script has to be modified, e.g., change from: command_args="--path.config ${LS_CONF_DIR} --path.data ${LS_DATA_DIR} --path.logs ${LS_LOG_DIR} --path.settings ${LS_SETTINGS_DIR} ${LS_OPTS}" to: command_args="--path.data ${LS_DATA_DIR} --path.logs ${LS_LOG_DIR} --path.settings ${LS_SETTINGS_DIR} ${LS_OPTS}" When the command line argument contains --path.config pipelines will not be loaded. Reproducible: Always Steps to Reproduce: 1. configure pipelines 2. start logstash Actual Results: no pipelines are loaded Expected Results: pipelines running Eventually this can be solved by setting an option in /etc/conf.d/logstash which decides to run logstash with or without pipelines.
Elastic seems to be using a different approach - the pipelines.yml contains the following: - pipeline.id: main path.config: "/etc/logstash/conf.d/*.conf" So this is backwards compatible.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ccbad95d8a5cc265e016d3cb27898bf0fd9db7e4 commit ccbad95d8a5cc265e016d3cb27898bf0fd9db7e4 Author: Tomas Mozes <hydrapolic@gmail.com> AuthorDate: 2018-07-13 13:55:22 +0000 Commit: Mikle Kolyada <zlogene@gentoo.org> CommitDate: 2018-07-15 16:16:50 +0000 app-admin/logstash-bin: bump to 6.3.1 Closes: https://bugs.gentoo.org/656828 Package-Manager: Portage-2.3.42, Repoman-2.3.9 app-admin/logstash-bin/Manifest | 1 + app-admin/logstash-bin/files/logstash.confd-r2 | 37 ++++++++++++ app-admin/logstash-bin/files/logstash.initd-r2 | 69 ++++++++++++++++++++++ app-admin/logstash-bin/files/pipelines.yml | 6 ++ app-admin/logstash-bin/logstash-bin-6.3.1.ebuild | 75 ++++++++++++++++++++++++ 5 files changed, 188 insertions(+)
