- Functionbeat Reference:
- Functionbeat overview
- Quick start: installation and configuration
- Set up and deploy
- Configure
- AWS 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_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- replace
- syslog
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- Regular expression support
- Instrumentation
- 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
- Publishing to Logstash fails with "connection reset by peer" message
- @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
- High RSS memory usage due to MADV settings
Functionbeat will reach End of Support on October 18, 2023. You should consider
moving your deployments to the more versatile and efficient Elastic Serverless
Forwarder.
Truncate fields
editTruncate fields
editThe truncate_fields
processor truncates a field to a given size. If the size of the field is smaller than
the limit, the field is left as is.
-
fields
-
List of fields to truncate. It’s supported to use
@metadata.
prefix for the fields and truncate values in the event metadata instead of event fields. -
max_bytes
-
Maximum number of bytes in a field. Mutually exclusive with
max_characters
. -
max_characters
-
Maximum number of characters in a field. Mutually exclusive with
max_bytes
. -
fail_on_error
-
(Optional) If set to true, in case of an error the changes to
the event are reverted, and the original event is returned. If set to
false
, processing continues also if an error happens. Default istrue
. -
ignore_missing
-
(Optional) Whether to ignore events that lack the source
field. The default is
false
, which will fail processing of an event if a field is missing.
For example, this configuration truncates the field named message
to 5 characters:
processors: - truncate_fields: fields: - message max_characters: 5 fail_on_error: false ignore_missing: true
Was this helpful?
Thank you for your feedback.