- Winlogbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting Started With Winlogbeat
- Setting up and running Winlogbeat
- Upgrading Winlogbeat
- Configuring Winlogbeat
- Set up Winlogbeat
- 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
- 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
- winlogbeat.reference.yml
- Exported Fields
- Securing Winlogbeat
- Troubleshooting
WARNING: Version 6.0 of Winlogbeat 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.
Filter and Enhance the exported data
editFilter and Enhance the exported data
editYou can define processors in your configuration to process events before they are sent to the configured output. The libbeat library provides processors for:
- reducing the number of exported fields
- enhancing events with additional metadata
- performing additional processing and decoding
Each processor receives an event, applies a defined action to the event, and returns the event. If you define a list of processors, they are executed in the order they are defined in the Winlogbeat configuration file.
event -> processor 1 -> event1 -> processor 2 -> event2 ...
For example, the following filter configuration drops a few fields that are rarely used (provider_guid
, process_id
, thread_id
, and version
) and one nested field, event_data.ErrorSourceTable
:
processors: - drop_fields: fields: [provider_guid, process_id, thread_id, version, event_data.ErrorSourceTable]