Description of the problem including expected versus actual behavior:
After merge of PR #15679 which introduced new Java classes for base, aliased and Boolean setting translating from Ruby existing code, if Logstash runs with the reload of a pipeline flag (both as command line --config.reload.automatic or configuring it in config/logstash.yml, it starts repeating the following error log:
[2024-10-03T14:03:12,018][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
This happens only when the pipeline is configured in config/pipelines.yml, both as config.string or with path path.config.
Instead, it doesn't happen when running directly the pipeline form the file with logstash -f simple_pipeline.conf
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
- edit
config/pipelines.yml adding
- pipeline.id: test
config.string: "input{ tcp { port => 12345 } } output { stdout{} }"
- Run Logstash with
bin/logstash --config.reload.automatic
If the reload it's not enabled, it doesn't happen.
Also note that it happend every 3 seconds (the default value of config.reload.interval) and appears always twice
Provide logs (if relevant):
[2024-10-03T14:12:36,209][INFO ][logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:test], :non_running_pipelines=>[]}
[2024-10-03T14:12:39,242][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
[2024-10-03T14:12:39,245][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
[2024-10-03T14:12:42,234][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
[2024-10-03T14:12:42,235][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
[2024-10-03T14:12:45,230][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
[2024-10-03T14:12:45,233][WARN ][org.logstash.settings.DeprecatedAlias] The value of setting `api.enabled` has been queried by its deprecated alias `http.enabled`. Code should be updated to query `api.enabled` instead
Description of the problem including expected versus actual behavior:
After merge of PR #15679 which introduced new Java classes for base, aliased and Boolean setting translating from Ruby existing code, if Logstash runs with the reload of a pipeline flag (both as command line
--config.reload.automaticor configuring it inconfig/logstash.yml, it starts repeating the following error log:This happens only when the pipeline is configured in
config/pipelines.yml, both asconfig.stringor with pathpath.config.Instead, it doesn't happen when running directly the pipeline form the file with
logstash -f simple_pipeline.confSteps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
config/pipelines.ymladdingIf the reload it's not enabled, it doesn't happen.
Also note that it happend every 3 seconds (the default value of
config.reload.interval) and appears always twiceProvide logs (if relevant):