Override input settings
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Behind the scenes, each module starts a Filebeat input. Advanced users can add or override any input settings. For example, you can set close_eof to true in the module configuration:
- module: nginx
access:
input:
close_eof: true
Or at the command line when you run Filebeat:
-M "nginx.access.input.close_eof=true"
You can use wildcards to change variables or settings for multiple modules/filesets at once. For example, you can enable close_eof for all the filesets in the nginx module:
-M "nginx.*.input.close_eof=true"
You can also enable close_eof for all inputs created by any of the modules:
-M "*.*.input.close_eof=true"