- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Configuring Filebeat
- Troubleshooting
- Getting Help
- Debugging
- Frequently Asked Questions
- Why can’t I read log files from network volumes?
- Why isn’t Filebeat collecting lines from my file?
- Why is Filebeat using too much CPU?
- Why is the dashboard in Kibana breaking up my data fields incorrectly?
- Why doesn’t my connection to Logstash work?
- Why is @metadata missing in Logstash?
- What is the difference between Logstash and Beats?
- Why does my SSL client fail to connect to Logstash?
- Migrating from Logstash Forwarder to Filebeat
- Reference
WARNING: Version 1.1 of Filebeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Step 3 (Optional): Configuring Filebeat to Use Logstash
editStep 3 (Optional): Configuring Filebeat to Use Logstash
editIf you want to use Logstash to perform additional processing on the data collected by Filebeat, you need to configure Filebeat to use Logstash.
To do this, you edit the Filebeat configuration file to disable the Elasticsearch output by commenting it out and enable the Logstash output by uncommenting the logstash section:
output: logstash: hosts: ["127.0.0.1:5044"] # Optional load balance the events between the Logstash hosts #loadbalance: true
In this configuration, hosts specifies the Logstash server and the port (5044)
where Logstash is configured to listen for incoming Beats connections.
To use this configuration, you must also set up Logstash to receive events from Beats.