- Auditbeat Reference: other versions:
- Overview
- Getting started with Auditbeat
- Breaking changes in 6.2
- Setting up and running Auditbeat
- Configuring Auditbeat
- Specify which modules to run
- Specify general settings
- Reload the configuration dynamically
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- 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
- Regular expression support
- HTTP Endpoint
- auditbeat.reference.yml
- Modules
- Exported fields
- Monitoring Auditbeat
- Securing Auditbeat
- Troubleshooting
- Contributing to Beats
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Drop fields from events
editDrop fields from events
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.