- Packetbeat Reference: other versions:
- Packetbeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade Packetbeat
- Configure
- Traffic sniffing
- Network flows
- Protocols
- Processes
- General settings
- Project paths
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Kibana endpoint
- Kibana dashboards
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Instrumentation
- packetbeat.reference.yml
- How to guides
- Exported fields
- AMQP fields
- Beat fields
- Cassandra fields
- Cloud provider metadata fields
- Common fields
- DHCPv4 fields
- DNS fields
- Docker fields
- ECS fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Jolokia Discovery autodiscover provider fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Process fields
- Raw fields
- Redis fields
- SIP fields
- Thrift-RPC fields
- Detailed TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitor
- Secure
- Visualize Packetbeat data in Kibana
- Troubleshoot
- Get help
- Debug
- Record a trace
- Common problems
- Dashboard in Kibana is breaking up data fields incorrectly
- Packetbeat doesn’t see any packets when using mirror ports
- Packetbeat can’t capture traffic from Windows loopback interface
- Packetbeat is missing long running transactions
- Packetbeat isn’t capturing MySQL performance data
- Packetbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- Dashboard could not locate the index-pattern
- Fields show up as nested JSON in Kibana
- Contribute to Beats
Load the Elasticsearch index template
editLoad the Elasticsearch index template
editElasticsearch uses index templates to define:
- Settings that control the behavior of your indices. The settings include the lifecycle policy used to manage indices as they grow and age.
- Mappings that determine how fields are analyzed. Each mapping sets the Elasticsearch datatype to use for a specific data field.
The recommended index template file for Packetbeat is installed by the
Packetbeat packages. If you accept the default configuration in the
packetbeat.yml
config file, Packetbeat loads the template automatically
after successfully connecting to Elasticsearch. If the template already exists,
it’s not overwritten unless you configure Packetbeat to do so.
A connection to Elasticsearch is required to load the index template. If the output is not Elasticsearch (or Elasticsearch Service), you must load the template manually.
This page shows how to change the default template loading behavior to:
For a full list of template setup options, see Elasticsearch index template.
Load your own index template
editTo load your own index template, set the following options:
setup.template.name: "your_template_name" setup.template.fields: "path/to/fields.yml"
If the template already exists, it’s not overwritten unless you configure Packetbeat to do so.
Overwrite an existing index template
editDo not enable this option for more than one instance of Packetbeat. If you start multiple instances at the same time, it can overload your Elasticsearch with too many template update requests.
To overwrite a template that’s already loaded into Elasticsearch, set:
setup.template.overwrite: true
Disable automatic index template loading
editYou may want to disable automatic template loading if you’re using an output other than Elasticsearch and need to load the template manually. To disable automatic template loading, set:
setup.template.enabled: false
If you disable automatic template loading, you must load the index template manually.
Load the index template manually
editTo load the index template manually, run the setup
command.
A connection to Elasticsearch is required. If another output is enabled, you need to
temporarily disable that output and enable Elasticsearch by using the -E
option.
The examples here assume that Logstash output is enabled.
You can omit the -E
flags if Elasticsearch output is already enabled.
If you are connecting to a secured Elasticsearch cluster, make sure you’ve configured credentials as described in the Quick start: installation and configuration.
If the host running Packetbeat does not have direct connectivity to Elasticsearch, see Load the index template manually (alternate method).
To load the template, use the appropriate command for your system.
Use sudo
to run these commands if the config file is owned by root.
deb and rpm:
packetbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
mac:
./packetbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
brew:
packetbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
linux:
./packetbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
docker:
docker run docker.elastic.co/beats/packetbeat:7.10.2 setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
win:
Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
From the PowerShell prompt, change to the directory where you installed Packetbeat, and run:
PS > .\packetbeat.exe setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'
Force Kibana to look at newest documents
editIf you’ve already used Packetbeat to index data into Elasticsearch,
the index may contain old documents. After you load the index template,
you can delete the old documents from packetbeat-*
to force Kibana to look
at the newest documents.
Use this command:
deb and rpm:
curl -XDELETE 'http://localhost:9200/packetbeat-*'
mac:
curl -XDELETE 'http://localhost:9200/packetbeat-*'
linux:
curl -XDELETE 'http://localhost:9200/packetbeat-*'
win:
PS > Invoke-RestMethod -Method Delete "http://localhost:9200/packetbeat-*"
This command deletes all indices that match the pattern packetbeat-*
.
Before running this command, make sure you want to delete all indices that match
the pattern.
Load the index template manually (alternate method)
editIf the host running Packetbeat does not have direct connectivity to Elasticsearch, you can export the index template to a file, move it to a machine that does have connectivity, and then install the template manually.
To export the index template, run:
deb and rpm:
packetbeat export template > packetbeat.template.json
mac:
./packetbeat export template > packetbeat.template.json
brew:
packetbeat export template > packetbeat.template.json
linux:
./packetbeat export template > packetbeat.template.json
win:
PS > .\packetbeat.exe export template --es.version 7.10.2 | Out-File -Encoding UTF8 packetbeat.template.json
To install the template, run:
deb and rpm:
curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_template/packetbeat-7.10.2 -d@packetbeat.template.json
mac:
curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_template/packetbeat-7.10.2 -d@packetbeat.template.json
linux:
curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_template/packetbeat-7.10.2 -d@packetbeat.template.json
win:
PS > Invoke-RestMethod -Method Put -ContentType "application/json" -InFile packetbeat.template.json -Uri http://localhost:9200/_template/packetbeat-7.10.2
On this page