Type to search.

Decode Base64 fields

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    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.

The 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.

YAML 
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 base64 decode 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.