Decode Base64 fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The decode_base64_field processor specifies a field to base64 decode.
To overwrite fields, either rename the target field or use the drop_fields processor to drop the field, and then rename the field.
In this example, field1 is decoded in field2.
- decode_base64_field:
field:
from: "field1"
to: "field2"
ignore_missing: false
fail_on_error: true
Elastic Agent processors execute before ingest pipelines, which means that your processor configurations cannot refer to fields that are created by ingest pipelines or Logstash. For more limitations, refer to What are some limitations of using processors?
| Name | Required | Default | Description |
|---|---|---|---|
field |
Yes | Contains: * from: "old-key", where from is the origin* to: "new-key", where to is the target field name |
|
ignore_missing |
No | false |
Whether to ignore missing keys. If true, missing keys that should be base64 decoded are ignored and no error is logged. If false, an error is logged and the behavior of fail_on_error is applied. |
fail_on_error |
No | true |
Whether to fail if an error occurs. If true and an error occurs, an error is logged and the event is dropped. If false, an error is logged, but the event is not modified. |
See Conditions for a list of supported conditions.