- Winlogbeat Reference: other versions:
- Overview
- 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
- Configure index lifecycle management
- Specify SSL settings
- Filter and Enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Decode Base64 fields
- Decompress gzip fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Script Processor
- Timestamp
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure 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
- winlogbeat.reference.yml
- Modules
- Exported fields
- Monitoring Winlogbeat
- Securing Winlogbeat
- Troubleshooting
- Get Help
- Debug
- Common problems
- Dashboard in Kibana is breaking up data fields incorrectly
- Bogus computer_name fields are reported in some events
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- @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
- Not sure how to read from .evtx files
- 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.
Decode Base64 fields
editDecode Base64 fields
editThe decode_base64_field processor specifies a field to base64 decode.
The field key contains a from: old-key and a to: new-key pair. from is
the origin and to the target name of the field.
To overwrite fields either first rename the target field or use the drop_fields
processor to drop the field and then rename the field.
processors: - decode_base64_field: field: from: "field1" to: "field2" ignore_missing: false fail_on_error: true
In the example above: - field1 is decoded in field2
The decode_base64_field processor has the following configuration settings:
-
ignore_missing -
(Optional) If set to true, no error is logged in case a key
which should be base64 decoded is missing. Default is
false. -
fail_on_error -
(Optional) If set to true, in case of an error the base6 4decode
of fields is stopped and the original event is returned. If set to false, decoding
continues also if an error happened during decoding. Default is
true.
See Conditions for a list of supported conditions.
Was this helpful?
Thank you for your feedback.