- Packetbeat Reference: other versions:
- Overview
- Getting Started With Packetbeat
- Upgrading Packetbeat
- Configuring Packetbeat
- Configuration Options (Reference)
- Network Device Configuration
- Flows Configuration
- Transaction Protocols Configuration
- Monitored Processes Configuration
- General Configuration
- Elasticsearch Output Configuration
- Logstash Output Configuration
- Kafka Output Configuration
- Redis Output Configuration
- File Output Configuration
- Console Output Configuration
- SSL Configuration
- Paths Configuration
- Logging Configuration
- Run Options Configuration
- Processors
- Filtering and Enhancing the Exported Data
- Configuring Packetbeat to Use Ingest Node
- Exporting GeoIP Information
- Configuring Packetbeat to Use Logstash
- Using Environment Variables in the Configuration
- Setting Traffic Capturing Options
- Configuring Thrift-RPC Support
- Maintaining the Real-Time State of the Network Topology
- YAML Tips and Gotchas
- Configuration Options (Reference)
- Exported Fields
- AMQP Fields
- Beat Fields
- Cassandra Fields
- Cloud Provider Metadata Fields
- Common Fields
- DNS Fields
- Flow Event Fields
- HTTP Fields
- ICMP Fields
- Memcache Fields
- MongoDb Fields
- MySQL Fields
- NFS Fields
- PostgreSQL Fields
- Raw Fields
- Redis Fields
- Thrift-RPC Fields
- Transaction Event Fields
- Measurements (Transactions) Fields
- Securing Packetbeat
- Visualizing Packetbeat Data in Kibana
- Troubleshooting
- Developer Guide: Adding a New Protocol
WARNING: Version 5.2 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.
drop_fields
editdrop_fields
editThe drop_fields processor specifies which fields to drop if a certain
condition is fulfilled. The condition is optional. If it’s missing, the
specified fields are always dropped. The @timestamp and type fields cannot
be dropped, even if they show up in the drop_fields list.
processors: - drop_fields: when: condition fields: ["field1", "field2", ...]
See Conditions for a list of supported conditions.
If you define an empty list of fields under drop_fields, then no fields
are dropped.
Was this helpful?
Thank you for your feedback.