WARNING: Version 1.1 of Packetbeat 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 2: Configuring Packetbeat Step 4: Loading the Index Template in Elasticsearch »
Elastic Docs ›Packetbeat Reference [1.1] ›Getting Started With Packetbeat

Step 3 (Optional): Configuring Packetbeat to Use Logstash

edit

Step 3 (Optional): Configuring Packetbeat to Use Logstash

edit

If you want to use Logstash to perform additional processing on the data collected by Packetbeat, you need to configure Packetbeat to use Logstash.

To do this, you edit the Packetbeat 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.

« Step 2: Configuring Packetbeat Step 4: Loading the Index Template in Elasticsearch »