Type to search.

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

This configuration truncates the field named message to five characters:

YAML
- truncate_fields:
    fields:
      - message
    max_characters: 5
    fail_on_error: false
    ignore_missing: true
Note

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
fields Yes List of fields to truncate. You can use the @metadata. prefix to truncate values in the event metadata instead of event fields.
max_bytes Yes Maximum number of bytes in a field. Mutually exclusive with max_characters.
max_characters Yes Maximum number of characters in a field. Mutually exclusive with max_bytes.
fail_on_error No true If true and an error occurs, any changes to the event are reverted, and the original event is returned. If false, processing continues even if an error occurs.
ignore_missing No false Whether to ignore events that lack the source field. If false, processing of the event fails if a field is missing.