- Packetbeat Reference: other versions:
- Overview
- Getting started with Packetbeat
- Setting up and running Packetbeat
- Upgrading Packetbeat
- Configuring 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
- Set up index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Parse data 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
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- HTTP Endpoint
- packetbeat.reference.yml
- Exported fields
- Alias fields
- AMQP fields
- Beat fields
- Cassandra fields
- Cloud provider metadata fields
- Common fields
- DHCPv4 fields
- DNS fields
- Docker fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Raw fields
- Redis fields
- Thrift-RPC fields
- TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitoring Packetbeat
- Securing Packetbeat
- Visualizing Packetbeat data in Kibana
- Troubleshooting
- Contributing to Beats
Packetbeat features that require authorization
editPacketbeat features that require authorization
editAfter securing Packetbeat, make sure your users have the roles (or associated privileges) required to use these Packetbeat features. Note that some of the roles shown here are built-in, and some are user-defined.
| Feature | Role |
|---|---|
Send data to a secured cluster |
|
Load index templates |
|
Load Packetbeat dashboards into Kibana |
|
Load machine learning jobs |
|
Read indices created by Packetbeat |
|
View Packetbeat dashboards in Kibana |
|
Load index lifecycle policies and use index lifecycle management |
|
To create the user-defined roles shown here, see Configure authentication credentials and Grant users access to Packetbeat indices. You may want to define additional roles to provide more restrictive access.