6.8.9
When using external config files, it is unclear what input settings are actually allowed under the filebeat.config.inputs construct. For example, if the user configures clean_inactive under filebeat.config.inputs, it does not throw a configuration error and treats it as a valid config, but it doesn't appear to apply to the inputs that are configured within the external files.
filebeat.config.inputs:
enabled: true
path: prospectors/*.yml
clean_inactive: 24h
Specifying these settings within the external configuration files work. While the example on this page does show that scan_frequency is configured as part of the input block, because we are accepting these settings at the filebeat.config.inputs level, it will be helpful to clarify that these settings must all go into the external files, etc..
6.8.9
When using external config files, it is unclear what input settings are actually allowed under the
filebeat.config.inputsconstruct. For example, if the user configures clean_inactive underfilebeat.config.inputs, it does not throw a configuration error and treats it as a valid config, but it doesn't appear to apply to the inputs that are configured within the external files.Specifying these settings within the external configuration files work. While the example on this page does show that scan_frequency is configured as part of the input block, because we are accepting these settings at the
filebeat.config.inputslevel, it will be helpful to clarify that these settings must all go into the external files, etc..