WARNING: Version 6.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.
Configuring Packetbeat
editConfiguring Packetbeat
editBefore modifying configuration settings, make sure you’ve completed the configuration steps in the Getting Started. This section describes some common use cases for changing configuration options.
To configure Packetbeat, you edit the configuration file. For rpm and deb,
you’ll find the configuration file at /etc/packetbeat/packetbeat.yml.
There’s also a full example configuration file at
/etc/packetbeat/packetbeat.reference.yml that shows all non-deprecated
options. For mac and win, look in the archive that you extracted.
The Packetbeat configuration file uses YAML for its syntax. See the Config File Format section of the Beats Platform Reference for more about the structure of the config file.
The following topics describe how to configure Packetbeat:
- Set traffic capturing options
- Set up flows to monitor network traffic
- Specify which transaction protocols to monitor
- Specify which processes to monitor
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse logs by using ingest node
- Export GeoIP Information
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Set up logging
- Use environment variables in the configuration
- YAML tips and gotchas
- packetbeat.reference.yml