Configuring Filebeat inputs determines which log files or data sources are collected. By specifying paths, multiline settings, or exclude patterns, you control what data is forwarded.
Filebeat supports multiple input types like log files, syslog, or modules. Proper configuration ensures only relevant data is ingested, reducing noise and storage costs.
Well-tuned inputs provide cleaner, more focused datasets for Logstash or Elasticsearch consumption.
Steps to configure Filebeat inputs:
- Open the main Filebeat configuration file.
$ sudo nano /etc/filebeat/filebeat.yml (no direct output)
Locate the filebeat.inputs section in the YAML file.
- Add a type: log input and specify file paths.
Use wildcards in paths if logs are split by date or host.
- Configure exclude_lines or include_lines to filter logs.
- Enable multiline settings if a single event spans multiple lines.
- Test configuration.
$ sudo filebeat test config Config OK
Incorrect file paths or YAML syntax can break the configuration.
- Restart Filebeat to apply changes.
$ sudo systemctl restart filebeat (no output)
Check Filebeat logs to confirm new inputs are being processed.

Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.
Comment anonymously. Login not required.