-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc: Clarify where input settings should be placed when using filebeat.config.inputs #19148
Comments
Pinging @elastic/integrations-services (Team:Services) |
I looked through the Filebeat code, specifically this path:
According to the code, we are not expecting any input settings to be specified directly under |
Clarify that all input type configuration options must be specified within the external configuration file: #19148
Thanks for confirming! Submitted a PR to clarify documentation until we start validating configuration settings for Beats. |
Clarify that all input type configuration options must be specified within the external configuration file: #19148
Clarify that all input type configuration options must be specified within the external configuration file: elastic#19148
Closed by #19284 |
Clarify that all input type configuration options must be specified within the external configuration file: elastic#19148
Clarify that all input type configuration options must be specified within the external configuration file: #19148 Co-authored-by: Pius <[email protected]>
Clarify that all input type configuration options must be specified within the external configuration file: #19148 Co-authored-by: Pius <[email protected]>
Clarify that all input type configuration options must be specified within the external configuration file: elastic#19148 Co-authored-by: Pius <[email protected]>
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 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.inputs
level, it will be helpful to clarify that these settings must all go into the external files, etc..The text was updated successfully, but these errors were encountered: