- Functionbeat Reference:
- Overview
- Get started
- Set up and deploy
- Configure
- AWS functions
- Google functions
- General settings
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- Regular expression support
- functionbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Deployment to AWS fails with "failed to create the stack"
- Deployment to AWS fails with "resource limit exceeded"
- 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
A newer version is available. 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 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.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register nowWas this helpful?
Thank you for your feedback.